← previous blocknext block →recent activity
Analyzing
Block #84,620,763
12 transactions · 9 stateful · 2026-06-30 05:51:10 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,620,763 · 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
10w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40b5f387…a164
0x34b655…2a6f
4 touches
1 conflict
0x6ee1c861…bec2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x170e4e4c…2b90
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x7c6984da…21e5
0x34b655…2a6f
2 touches
0 conflicts
0x81d3b608…cefa
0x34b655…2a6f
2 touches
0 conflicts
0xa16b3e4e…0787
0x34b655…2a6f
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 0x40b5f38715…7ba164
Audit this contract →
← previous block·next block →recent activity