← previous blocknext block →recent activity
Analyzing
Block #96,300,572
7 transactions · 6 stateful · 2026-08-15 20:36:35 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,300,572 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fb66e8…4f94
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x000bde1a…e123
0x34b655…2a6f
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x143c16d2…5e4d
0x34b655…2a6f
2 touches
0 conflicts
0x16f2b4e1…e98b
0x34b655…2a6f
2 touches
0 conflicts
0x2d3930d3…c9b8
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 0xb7fb66e892…ec4f94
Audit this contract →
← previous block·next block →recent activity