← previous blocknext block →recent activity
Analyzing
Block #96,640,341
17 transactions · 16 stateful · 2026-08-17 01:05:46 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,640,341 · 17 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
1w03w05w16w27w08w19w310w411w512w014w116w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bdb9869…7558
0x34b655…2a6f
10 touches
10 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xdade69ff…a4a4
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x30621d87…1951
0x34b655…2a6f
6 touches
3 conflicts
0xd6bd849a…5597
0x2a68ba…90c5
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 0x6bdb9869c7…427558
Audit this contract →
← previous block·next block →recent activity