← previous blocknext block →recent activity
Analyzing
Block #96,373,111
11 transactions · 9 stateful · 2026-08-16 02:41:25 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.45
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,373,111 · 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
1w02w13w06w07w18w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf1faa605…f919
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x57bcf61d…bcbf
0x34b655…2a6f
4 touches
1 conflict
0x932a9590…0b19
0x34b655…2a6f
4 touches
1 conflict
0x9511d8da…efa1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
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
1 conflict on slot 0xf1faa605a5…02f919
Audit this contract →
← previous block·next block →recent activity