← previous blocknext block →recent activity
Analyzing
Block #84,046,319
14 transactions · 12 stateful · 2026-06-27 14:02:41 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,046,319 · 14 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
5w06w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac808a27…82db
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
0x34b655…2a6f
4 touches
1 conflict
0x0c7b231e…c0b8
0x34b655…2a6f
4 touches
1 conflict
0x636b2053…9114
0x34b655…2a6f
3 touches
1 conflict
0xee28d8b5…bd37
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c2
0x1b6862…e19c
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 0xac808a2776…3282db
Audit this contract →
← previous block·next block →recent activity