← previous blocknext block →recent activity
Analyzing
Block #96,491,181
21 transactions · 6 stateful · 2026-08-16 12:35:15 UTC
Parallelism
81/100
Blocked
50%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,491,181 · 21 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
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x1b5e05d0…4a66
0x34b655…2a6f
2 touches
0 conflicts
0x29f54601…4cda
0x34b655…2a6f
2 touches
0 conflicts
0x2ccaa29d…a823
0x34b655…2a6f
2 touches
0 conflicts
0x35b0198e…3e0d
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
6 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity