← previous blocknext block →recent activity
Analyzing
Block #84,350,980
18 transactions · 15 stateful · 2026-06-28 23:52:07 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,350,980 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w08w19w214w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x5d82c9b5…004c
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
6 touches
3 conflicts
0x86518ac6…3487
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xd25997d0…a684
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0005
0x5afd3e…7620
4 touches
1 conflict
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
3 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity