← previous blocknext block →recent activity
Analyzing
Block #84,115,031
20 transactions · 18 stateful · 2026-06-27 21:40:28 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,115,031 · 20 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
1w03w06w17w28w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
4 touches
1 conflict
0xce9524b5…6ea0
0x065c9d…c394
3 touches
1 conflict
0xf59f0974…9003
0x065c9d…c394
3 touches
1 conflict
0xf8127de7…d5ec
0x3bd359…433a
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