← previous blocknext block →recent activity
Analyzing
Block #84,359,497
16 transactions · 11 stateful · 2026-06-29 00:48:59 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,359,497 · 16 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
1w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7a7fc8dc…fd4d
0x5afd3e…7620
4 touches
1 conflict
0xbb521fc5…8ca3
0x5afd3e…7620
4 touches
1 conflict
0x0a1494e1…25fc
0x5afd3e…7620
4 touches
1 conflict
0x4f703a27…2a1d
0x5afd3e…7620
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
2 touches
0 conflicts
0x00000000…0004
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
2 touches
0 conflicts
0x4039b31f…0f4a
0x754704…b603
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 0x7a7fc8dcc9…17fd4d
Audit this contract →
← previous block·next block →recent activity