← previous blocknext block →recent activity
Analyzing
Block #84,347,327
14 transactions · 13 stateful · 2026-06-28 23:27:45 UTC
Parallelism
86/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,347,327 · 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
1w02w13w05w06w19w010w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd32efc7…b2e3
0x5afd3e…7620
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x72b88fe4…2a1c
0x5afd3e…7620
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x3d06cabe…bf5b
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0019
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: Liquidity Book Token (LBT)
1 conflict on slot 0xfd32efc712…4fb2e3
Audit this contract →
← previous block·next block →recent activity