← previous blocknext block →recent activity
Analyzing
Block #84,305,452
9 transactions · 8 stateful · 2026-06-28 18:48:47 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,305,452 · 9 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x826cce18…251c
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x055a7943…c67a
0x34b655…2a6f
3 touches
1 conflict
0x23cf86bd…b4a9
0x34b655…2a6f
3 touches
1 conflict
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d619
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d61b
0xea1b8e…c5ec
2 touches
0 conflicts
0x9c8d6dd6…d61c
0xea1b8e…c5ec
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 0x826cce18ca…e5251c
Audit this contract →
← previous block·next block →recent activity