← previous blocknext block →recent activity
Analyzing
Block #84,237,559
14 transactions · 11 stateful · 2026-06-28 11:16:31 UTC
Parallelism
86/100
Blocked
9%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,237,559 · 14 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
1w04w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0x1b9d47af…db57
0x065c9d…c394
3 touches
1 conflict
0xbf38391b…dd98
0xd32edf…ff58
3 touches
1 conflict
0x40e2d65d…2a35
0x3bd359…433a
2 touches
0 conflicts
0x99f666e3…b2a2
0x3bd359…433a
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
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 0x92d610a6f9…379a40
Audit this contract →
← previous block·next block →recent activity