← previous blocknext block →recent activity
Analyzing
Block #84,524,383
15 transactions · 13 stateful · 2026-06-29 19:08:19 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,524,383 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w010w111w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56785e37…a197
0x065c9d…c394
4 touches
1 conflict
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x9ff2b017…3fa2
0x34b655…2a6f
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
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: Market-MON/USDC
1 conflict on slot 0x56785e3778…33a197
Audit this contract →
← previous block·next block →recent activity