← previous blocknext block →recent activity
Analyzing
Block #96,637,912
20 transactions · 18 stateful · 2026-08-17 00:53:33 UTC
Parallelism
65/100
Blocked
39%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,637,912 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w06w19w211w012w315w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8252706a…7ca5
0x34b655…2a6f
10 touches
10 conflicts
0x2d651956…12e8
0x34b655…2a6f
10 touches
10 conflicts
0x81681867…64fa
0x34b655…2a6f
6 touches
3 conflicts
0xaba6578d…bd48
0x34b655…2a6f
6 touches
3 conflicts
0xdf0b4e17…ccd8
0x34b655…2a6f
6 touches
3 conflicts
0xe999cbf5…d18a
0x34b655…2a6f
6 touches
3 conflicts
0x702cd11f…652b
0x34b655…2a6f
6 touches
3 conflicts
0x6bf457e3…9576
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
10 conflicts on slot 0x8252706a8a…797ca5
Audit this contract →
← previous block·next block →recent activity