← previous blocknext block →recent activity
Analyzing
Block #96,282,060
10 transactions · 8 stateful · 2026-08-15 19:03:28 UTC
Parallelism
60/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,282,060 · 10 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
2w03w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60d732ff…3b8a
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3ba883f0…d9f5
0x34b655…2a6f
2 touches
0 conflicts
0x427dec7f…61c6
0x34b655…2a6f
2 touches
0 conflicts
0x58b8a729…145c
0x34b655…2a6f
2 touches
0 conflicts
0x67209a5a…ab0e
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 0x60d732ff03…003b8a
Audit this contract →
← previous block·next block →recent activity