← previous blocknext block →recent activity
Analyzing
Block #96,086,832
12 transactions · 11 stateful · 2026-08-15 02:41:30 UTC
Parallelism
42/100
Blocked
55%
Avg conflicts / tx
1.42
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,086,832 · 12 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w37w48w510w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x979d8133…de18
0x34b655…2a6f
8 touches
6 conflicts
0xff196840…a453
0x34b655…2a6f
8 touches
6 conflicts
0x8702a009…24b2
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xbad8132b…ce44
0x34b655…2a6f
5 touches
3 conflicts
0x588380ee…0a5c
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 0x979d8133e4…09de18
Audit this contract →
← previous block·next block →recent activity