← previous blocknext block →recent activity
Analyzing
Block #84,597,638
10 transactions · 9 stateful · 2026-06-30 03:17:06 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,597,638 · 10 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
2w03w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0xb98b9e9d…a785
0x3bd359…433a
2 touches
0 conflicts
0x4e544201…5e2f
0x5afd3e…7620
2 touches
0 conflicts
0x63091d17…493d
0x5afd3e…7620
2 touches
0 conflicts
0xaf14377f…d149
0x5afd3e…7620
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: Liquidity Book Token (LBT)
1 conflict on slot 0x0000000000…000004
Audit this contract →
← previous block·next block →recent activity