← previous blocknext block →recent activity
Analyzing
Block #96,294,136
12 transactions · 9 stateful · 2026-08-15 20:04:12 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,294,136 · 12 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
6w07w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2aab0897…78f7
0x34b655…2a6f
4 touches
1 conflict
0x5adda4a7…b840
0x34b655…2a6f
4 touches
1 conflict
0x5df7cf2b…bbe5
0x34b655…2a6f
4 touches
1 conflict
0xfa98c6e8…0748
0x34b655…2a6f
4 touches
1 conflict
0xfa98c6e8…0747
0x34b655…2a6f
4 touches
1 conflict
0x454f33a1…9629
0x34b655…2a6f
3 touches
1 conflict
0x41d6652b…dfdd
0x34b655…2a6f
3 touches
1 conflict
0xbb97db90…4c93
0xc8689a…ee79
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 0x2aab08973a…f178f7
Audit this contract →
← previous block·next block →recent activity