← previous blocknext block →recent activity
Analyzing
Block #96,686,761
11 transactions · 8 stateful · 2026-08-17 04:59:13 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,686,761 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x434010de…83fe
0x34b655…2a6f
4 touches
1 conflict
0xb5a47a02…d364
0x34b655…2a6f
3 touches
1 conflict
0x288e0ff4…f2bf
0x34b655…2a6f
2 touches
0 conflicts
0x35312bd9…5ef1
0x34b655…2a6f
2 touches
0 conflicts
0x39a831a9…ff5d
0x34b655…2a6f
2 touches
0 conflicts
0x3f1a31b5…9888
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity