← previous blocknext block →recent activity
Analyzing
Block #84,352,222
18 transactions · 16 stateful · 2026-06-29 00:00:25 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,352,222 · 18 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
1w012w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a83dd8…da7c
0x065c9d…c394
4 touches
1 conflict
0xc24863d1…ee8d
0x065c9d…c394
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
2 touches
0 conflicts
0x36acc830…74d1
0x065c9d…c394
2 touches
0 conflicts
0x3c4b02ce…6626
0x065c9d…c394
2 touches
0 conflicts
0x4dfbbf9d…a641
0x065c9d…c394
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity