← previous blocknext block →recent activity
Analyzing
Block #96,371,750
10 transactions · 7 stateful · 2026-08-16 02:34:34 UTC
Parallelism
70/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,371,750 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8755cbdc…7b3e
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x19e1da6e…4a72
0x34b655…2a6f
4 touches
1 conflict
0x03c34ccb…3192
0x34b655…2a6f
2 touches
0 conflicts
0x03c38bff…f48f
0x34b655…2a6f
2 touches
0 conflicts
0x1d778644…7bb9
0x34b655…2a6f
2 touches
0 conflicts
0x24a44095…ee07
0x34b655…2a6f
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 0x8755cbdc7f…2d7b3e
Audit this contract →
← previous block·next block →recent activity