← previous blocknext block →recent activity
Analyzing
Block #96,018,422
11 transactions · 10 stateful · 2026-08-14 20:57:24 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,018,422 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabc640e3…7cc2
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe496cb47…01f5
0x34b655…2a6f
4 touches
1 conflict
0x02fdb0e0…b418
0x34b655…2a6f
4 touches
1 conflict
0x67a56c8b…f955
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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
3 conflicts on slot 0xabc640e307…577cc2
Audit this contract →
← previous block·next block →recent activity