← previous blocknext block →recent activity
Analyzing
Block #84,513,641
26 transactions · 21 stateful · 2026-06-29 17:56:43 UTC
Parallelism
77/100
Blocked
52%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,513,641 · 26 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w09w111w112w013w114w215w316w217w423w525w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…0012
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…001a
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…001b
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…001c
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…0022
0x74d80e…25d4
6 touches
3 conflicts
0x00000000…0002
0x74d80e…25d4
6 touches
3 conflicts
0x22e0cc1d…ad0d
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: 0x74d80ee4…0b25d4
3 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity