← previous blocknext block →recent activity
Analyzing
Block #96,309,740
14 transactions · 14 stateful · 2026-08-15 21:22:41 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,309,740 · 14 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
1w03w16w17w08w210w312w013w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a8ffca…8de2
0x34b655…2a6f
6 touches
3 conflicts
0xff196840…a453
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x784eaad2…d177
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
0x34b655…2a6f
4 touches
1 conflict
0x1cdfe548…d3aa
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
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: Perpl
3 conflicts on slot 0xa5a8ffca31…818de2
Audit this contract →
← previous block·next block →recent activity