← previous blocknext block →recent activity
Analyzing
Block #84,460,549
23 transactions · 23 stateful · 2026-06-29 12:02:26 UTC
Parallelism
78/100
Blocked
48%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,460,549 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w29w310w011w114w015w216w117w219w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0xb6836671…5c3c
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x14e88031…7799
0x34b655…2a6f
4 touches
1 conflict
0x1e346a85…e9c5
0x34b655…2a6f
4 touches
1 conflict
0x35de07e6…7751
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
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: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity