← previous blocknext block →recent activity
Analyzing
Block #107,442,010
16 transactions · 16 stateful · 2026-09-23 22:36:18 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,442,010 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w210w211w312w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0x51cff9ab…28bc
0x37db7f…ec7b
4 touches
1 conflict
0x6286219a…0721
0x37db7f…ec7b
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x3cb7ee74…b8a5
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x8fa4ba1b…750c
0x34b655…2a6f
4 touches
1 conflict
0xb086485b…10b4
0x34b655…2a6f
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
3 conflicts on slot 0x8a35acfbc1…6bd1b1
Audit this contract →
← previous block·next block →recent activity