← previous blocknext block →recent activity
Analyzing
Block #84,357,254
12 transactions · 9 stateful · 2026-06-29 00:34:00 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,357,254 · 12 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x8c1c1e82…c21c
0x40c49f…2af0
4 touches
1 conflict
0x7263b4fb…09dc
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3ad3efeb…c048
0x065c9d…c394
2 touches
0 conflicts
0x6503e479…8e6e
0x065c9d…c394
2 touches
0 conflicts
0x784a1301…bffa
0x065c9d…c394
2 touches
0 conflicts
0x7fde3225…02fc
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
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity