← previous blocknext block →recent activity
Analyzing
Block #82,564,455
13 transactions · 13 stateful · 2026-06-20 17:05:20 UTC
Parallelism
69/100
Blocked
23%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,564,455 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0x6863d5d1…05e7
0x065c9d…c394
3 touches
1 conflict
0x50da2f5b…0bda
0x065c9d…c394
3 touches
1 conflict
0xb7f5bbcb…5ab2
0x065c9d…c394
3 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x08913286…f0df
0x34b655…2a6f
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity