← previous blocknext block →recent activity
Analyzing
Block #84,178,891
11 transactions · 9 stateful · 2026-06-28 04:45:29 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,178,891 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x116b58c5…27f2
0x065c9d…c394
2 touches
0 conflicts
0x4ef6716d…2f8a
0x065c9d…c394
2 touches
0 conflicts
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x70af1dc3…e81e
0x065c9d…c394
2 touches
0 conflicts
0x87f069c9…0196
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: Market-MON/USDC
1 conflict on slot 0xff96dc9b2f…5a93d7
Audit this contract →
← previous block·next block →recent activity