← previous blocknext block →recent activity
Analyzing
Block #82,793,287
20 transactions · 13 stateful · 2026-06-21 18:35:39 UTC
Parallelism
90/100
Blocked
15%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,793,287 · 20 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
1w02w14w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0ff80c8a…d4bb
0x065c9d…c394
4 touches
1 conflict
0xb624d2ea…8c87
0x34b655…2a6f
4 touches
1 conflict
0xffc3d4dd…5c53
0x065c9d…c394
3 touches
1 conflict
0x30f0fa93…fe92
0x065c9d…c394
2 touches
0 conflicts
0x703be335…e951
0x065c9d…c394
2 touches
0 conflicts
0x80afd9d9…57cf
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