← previous blocknext block →recent activity
Analyzing
Block #84,118,962
22 transactions · 13 stateful · 2026-06-27 22:06:42 UTC
Parallelism
91/100
Blocked
23%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,118,962 · 22 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
1w02w13w06w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x6d81297c…12e2
0x40c49f…2af0
2 touches
0 conflicts
0x75f37100…f832
0x40c49f…2af0
2 touches
0 conflicts
0xb9f44c6b…79b6
0x40c49f…2af0
2 touches
0 conflicts
0xf2daa8fd…de50
0x40c49f…2af0
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity