← previous blocknext block →recent activity
Analyzing
Block #84,996,407
22 transactions · 18 stateful · 2026-07-01 23:34:22 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.73
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,996,407 · 22 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
1w03w04w15w26w37w48w59w111w214w619w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x8d0e1d29…cd3e
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x424eca3b…f2ab
0xa6afd3…d132
6 touches
3 conflicts
0x78c30df4…c54d
0xa6afd3…d132
6 touches
3 conflicts
0xf412c531…d397
0xa6afd3…d132
6 touches
3 conflicts
0x1bfc029c…f91e
0x34b655…2a6f
6 touches
3 conflicts
0x1f36ea17…fe37
0x34b655…2a6f
6 touches
3 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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity