← previous blocknext block →recent activity
Analyzing
Block #84,184,769
20 transactions · 17 stateful · 2026-06-28 05:24:36 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #84,184,769 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w17w310w311w412w513w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
14 touches
21 conflicts
0x31c6cbff…e613
0xd32edf…ff58
7 touches
6 conflicts
0xd25997d0…a689
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 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: Kuru Exchange: MarginAccount
21 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity