← previous blocknext block →recent activity
Analyzing
Block #96,520,568
15 transactions · 13 stateful · 2026-08-16 15:03:21 UTC
Parallelism
67/100
Blocked
31%
Avg conflicts / tx
0.67
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,520,568 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34b222ef…4afc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xfdf651e2…71e0
0x34b655…2a6f
4 touches
1 conflict
0x0ed7cc0b…ee52
0x34b655…2a6f
4 touches
1 conflict
0x5e7e0120…7bb9
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
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
6 conflicts on slot 0x34b222ef5c…ca4afc
Audit this contract →
← previous block·next block →recent activity