← previous blocknext block →recent activity
Analyzing
Block #107,450,396
21 transactions · 16 stateful · 2026-09-23 23:18:30 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,450,396 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w210w012w115w117w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a35acfb…d1b2
0x37db7f…ec7b
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x8a35acfb…d1b1
0x37db7f…ec7b
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x662d9b98…0f6b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x051a10a8…7d4e
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
3 conflicts on slot 0x8a35acfbc1…6bd1b2
Audit this contract →
← previous block·next block →recent activity