← previous blocknext block →recent activity
Analyzing
Block #84,357,564
27 transactions · 22 stateful · 2026-06-29 00:36:03 UTC
Parallelism
81/100
Blocked
45%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,357,564 · 27 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w111w012w113w214w317w018w119w220w222w324w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd16ba145…d030
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x75194ada…a1c5
0x34b655…2a6f
6 touches
3 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc3464910…786f
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 0xd16ba145e0…8cd030
Audit this contract →
← previous block·next block →recent activity