← previous blocknext block →recent activity
Analyzing
Block #84,564,271
18 transactions · 17 stateful · 2026-06-29 23:34:46 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,564,271 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w010w111w213w214w315w316w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
6 touches
3 conflicts
0xa7e45018…b59c
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcd
0x34b655…2a6f
6 touches
3 conflicts
0xfe3876ba…0946
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
0x6c6f37ba…c20b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
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
3 conflicts on slot 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity