← previous blocknext block →recent activity
Analyzing
Block #96,192,032
20 transactions · 17 stateful · 2026-08-15 11:30:39 UTC
Parallelism
65/100
Blocked
35%
Avg conflicts / tx
1.1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,192,032 · 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
3w04w15w28w09w315w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4c188934…158e
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfdd655b8…bf89
0x34b655…2a6f
4 touches
1 conflict
0x76c4467d…ce28
0x34b655…2a6f
4 touches
1 conflict
0x973729b4…d3fb
0x34b655…2a6f
4 touches
1 conflict
0xc807a400…b958
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
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
21 conflicts on slot 0x4c18893450…c5158e
Audit this contract →
← previous block·next block →recent activity