← previous blocknext block →recent activity
Analyzing
Block #84,023,290
15 transactions · 14 stateful · 2026-06-27 11:29:19 UTC
Parallelism
87/100
Blocked
29%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,023,290 · 15 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
2w03w06w17w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3261f99f…f018
0x065c9d…c394
4 touches
1 conflict
0xbd68c7c7…40b3
0x34b655…2a6f
4 touches
1 conflict
0x66203046…39d1
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbfb0d3e0…0161
0x065c9d…c394
3 touches
1 conflict
0xf0c46249…e8ca
0x065c9d…c394
3 touches
1 conflict
0xf9655020…bbdd
0x065c9d…c394
3 touches
1 conflict
0x877dfaa1…bb27
0x065c9d…c394
3 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 0x3261f99f87…b3f018
Audit this contract →
← previous block·next block →recent activity