← previous blocknext block →recent activity
Analyzing
Block #96,219,083
15 transactions · 15 stateful · 2026-08-15 13:46:43 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,219,083 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xba352368…cbf1
0x34b655…2a6f
4 touches
2 conflicts
0x35fa3923…4a21
0x34b655…2a6f
4 touches
1 conflict
0x388633a0…86cd
0x34b655…2a6f
4 touches
1 conflict
0x463caddd…1bf4
0x34b655…2a6f
4 touches
1 conflict
0x67209a5a…ab0e
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 0x0f2d78b1bb…5e7363
Audit this contract →
← previous block·next block →recent activity