← previous blocknext block →recent activity
Analyzing
Block #82,805,017
20 transactions · 13 stateful · 2026-06-21 19:54:00 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #82,805,017 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w26w37w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x21898044…a071
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xda1a4a4e…f7ef
0x065c9d…c394
3 touches
1 conflict
0x230a4710…1a2c
0x065c9d…c394
3 touches
1 conflict
0xca1df2c5…0f90
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity