← previous blocknext block →recent activity
Analyzing
Block #96,135,077
16 transactions · 15 stateful · 2026-08-15 06:44:13 UTC
Parallelism
81/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,135,077 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4d971bc9…fadc
0x34b655…2a6f
4 touches
1 conflict
0x4d971bc9…fadd
0x34b655…2a6f
4 touches
1 conflict
0x66df9b95…071b
0x34b655…2a6f
3 touches
1 conflict
0xfea142d7…d423
0x0a3323…0a3c
2 touches
0 conflicts
0xdd50e9b9…914b
0x1efe02…37d6
2 touches
0 conflicts
0x63f5c02f…6853
0x3bd359…433a
2 touches
0 conflicts
0x338a70cd…da47
0x754704…b603
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity