← previous blocknext block →recent activity
Analyzing
Block #84,404,317
31 transactions · 29 stateful · 2026-06-29 05:47:45 UTC
Parallelism
74/100
Blocked
52%
Avg conflicts / tx
1.61
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,404,317 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w522w626w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2e45419…f17b
0x34b655…2a6f
14 touches
21 conflicts
0x5df6102c…6494
0xa6afd3…d132
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x40970e69…da50
0x69df8a…6292
12 touches
15 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
12 touches
15 conflicts
0xb05cd4f5…73d0
0x69df8a…6292
12 touches
15 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
21 conflicts on slot 0xe2e454194e…59f17b
Audit this contract →
← previous block·next block →recent activity