← previous blocknext block →recent activity
Analyzing
Block #84,332,643
17 transactions · 14 stateful · 2026-06-28 21:49:55 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,332,643 · 17 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
2w03w05w08w19w210w113w114w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x454d8940…cfe7
0x34b655…2a6f
8 touches
6 conflicts
0x3d4ec808…d43b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2f7781d6…e632
0x34b655…2a6f
6 touches
3 conflicts
0x55e297b9…10cc
0x34b655…2a6f
4 touches
1 conflict
0x97b0b2ee…4666
0x34b655…2a6f
4 touches
1 conflict
0x97d5efed…1aa4
0x34b655…2a6f
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
6 conflicts on slot 0x454d8940c1…fbcfe7
Audit this contract →
← previous block·next block →recent activity