← previous blocknext block →recent activity
Analyzing
Block #84,563,637
12 transactions · 12 stateful · 2026-06-29 23:30:32 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,563,637 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec1d7176…6f5e
0x34b655…2a6f
4 touches
1 conflict
0x1f0f261b…0e1d
0x065c9d…c394
4 touches
1 conflict
0x338e74b0…51f2
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa42e8482…b88f
0x34b655…2a6f
4 touches
1 conflict
0x73351a57…afa5
0x40c49f…2af0
2 touches
0 conflicts
0x9951b6b0…22d0
0x40c49f…2af0
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
1 conflict on slot 0xec1d7176e6…a86f5e
Audit this contract →
← previous block·next block →recent activity