← previous blocknext block →recent activity
Analyzing
Block #96,125,938
12 transactions · 12 stateful · 2026-08-15 05:58:12 UTC
Parallelism
58/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,125,938 · 12 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
2w03w15w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5abc901…166d
0x34b655…2a6f
8 touches
6 conflicts
0xea1b8c07…b969
0x34b655…2a6f
8 touches
6 conflicts
0x5b0edc1d…65d6
0x34b655…2a6f
4 touches
1 conflict
0x7ea60711…6098
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eeb
0x34b655…2a6f
4 touches
1 conflict
0x9b2d3bee…8eec
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
6 conflicts on slot 0xd5abc9010e…93166d
Audit this contract →
← previous block·next block →recent activity