← previous blocknext block →recent activity
Analyzing
Block #96,031,853
14 transactions · 14 stateful · 2026-08-14 22:04:57 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,031,853 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w27w08w310w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5692e125…1727
0x34b655…2a6f
6 touches
3 conflicts
0xd79e9cac…9f72
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb566e26f…6d5d
0x34b655…2a6f
4 touches
1 conflict
0xbda105bc…24a8
0x34b655…2a6f
4 touches
1 conflict
0xca0d00ce…5b43
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x1cd2652d…26a7
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 0x5692e1257d…711727
Audit this contract →
← previous block·next block →recent activity