← previous blocknext block →recent activity
Analyzing
Block #106,395,236
23 transactions · 21 stateful · 2026-09-20 06:46:12 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.61
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,395,236 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w06w07w19w111w012w013w114w015w117w118w219w320w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1927b58…f161
0x34b655…2a6f
8 touches
6 conflicts
0x3b53436c…2ec3
0x34b655…2a6f
6 touches
3 conflicts
0x206a4507…e6c3
0x34b655…2a6f
6 touches
3 conflicts
0x0407c5a8…572a
0x34b655…2a6f
4 touches
1 conflict
0x13b3e772…6835
0x34b655…2a6f
4 touches
1 conflict
0x38bc0e31…caaf
0x34b655…2a6f
4 touches
1 conflict
0x09fa858e…3d58
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xb1927b5859…36f161
Audit this contract →
← previous block·next block →recent activity