← previous blocknext block →recent activity
Analyzing
Block #84,065,268
15 transactions · 11 stateful · 2026-06-27 16:08:54 UTC
Parallelism
87/100
Blocked
9%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,065,268 · 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0db14692…b4c0
0x065c9d…c394
2 touches
0 conflicts
0x28be03b4…3c0a
0x065c9d…c394
2 touches
0 conflicts
0x7fa422ea…cfc9
0x065c9d…c394
2 touches
0 conflicts
0xc72296b1…a93a
0x065c9d…c394
2 touches
0 conflicts
0xe0f93627…0b02
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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