← previous blocknext block →recent activity
Analyzing
Block #107,442,703
12 transactions · 11 stateful · 2026-09-23 22:39:47 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.83
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,442,703 · 12 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
1w03w15w26w37w09w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b0
0x37db7f…ec7b
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe8a876d4…921a
0x37db7f…ec7b
4 touches
1 conflict
0xb75367ff…a2b7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe9693c23…43cc
0x34b655…2a6f
4 touches
1 conflict
0x143dba04…1b98
0x37db7f…ec7b
4 touches
1 conflict
0x4af2cce5…16c4
0x37db7f…ec7b
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: 0x37db7fbf…3eec7b
6 conflicts on slot 0x8a35acfbc1…6bd1b0
Audit this contract →
← previous block·next block →recent activity