← previous blocknext block →recent activity
Analyzing
Block #84,360,409
14 transactions · 12 stateful · 2026-06-29 00:55:04 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,360,409 · 14 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
1w02w14w26w012w113w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x16e1d1ac…430f
0x065c9d…c394
3 touches
1 conflict
0xd3cdac1a…d84c
0x065c9d…c394
3 touches
1 conflict
0x00000000…0006
0x010592…1c83
2 touches
0 conflicts
0x044e23ca…2366
0x010592…1c83
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
3 conflicts on slot 0x7d42dc8b22…fefdb6
Audit this contract →
← previous block·next block →recent activity