← previous blocknext block →recent activity
Analyzing
Block #84,411,140
19 transactions · 13 stateful · 2026-06-29 06:33:11 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,411,140 · 19 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
1w02w13w24w37w013w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x37427e8f…428f
0x34b655…2a6f
4 touches
1 conflict
0x99910689…8959
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xad32e2ec…fd33
0x065c9d…c394
3 touches
1 conflict
0x00000000…0002
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0004
0x453805…c7fd
2 touches
0 conflicts
0x00000000…0009
0x453805…c7fd
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 0x13a54fa2d3…a35ae3
Audit this contract →
← previous block·next block →recent activity