← previous blocknext block →recent activity
Analyzing
Block #96,268,028
7 transactions · 7 stateful · 2026-08-15 17:52:54 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,268,028 · 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
2w03w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d488000…3831
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0x2a2452fa…5f4b
0x34b655…2a6f
4 touches
1 conflict
0x1683a436…2c42
0x34b655…2a6f
2 touches
0 conflicts
0x2ffa0115…ed47
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
0x34b655…2a6f
2 touches
0 conflicts
0x5e0b8bbe…377b
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 0x0d488000e2…143831
Audit this contract →
← previous block·next block →recent activity