← previous blocknext block →recent activity
Analyzing
Block #84,253,551
13 transactions · 13 stateful · 2026-06-28 13:02:58 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,253,551 · 13 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe91256d2…c2d9
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x582a46ff…adf9
0x5afd3e…7620
4 touches
1 conflict
0x404314de…df1a
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x00000000…0001
0x8b0d32…7367
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 0xe91256d27d…90c2d9
Audit this contract →
← previous block·next block →recent activity