← previous blocknext block →recent activity
Analyzing
Block #96,212,195
8 transactions · 8 stateful · 2026-08-15 13:12:04 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,212,195 · 8 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
1w02w13w25w37w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x97505c03…adce
0x34b655…2a6f
4 touches
1 conflict
0xa8374d8a…5c02
0x34b655…2a6f
4 touches
1 conflict
0xba352368…cbf1
0x34b655…2a6f
4 touches
1 conflict
0xbf9d3917…2850
0x34b655…2a6f
4 touches
1 conflict
0x45b3c66c…b788
0x34b655…2a6f
4 touches
1 conflict
0xd1d4b611…00e1
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
3 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity