← previous blocknext block →recent activity
Analyzing
Block #82,638,802
12 transactions · 8 stateful · 2026-06-21 01:23:25 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,638,802 · 12 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdb294d4…a4e9
0x065c9d…c394
4 touches
1 conflict
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xe7f6fce1…ea18
0x065c9d…c394
3 touches
1 conflict
0x0c89f41e…2b54
0x065c9d…c394
3 touches
1 conflict
0x3617319a…2eff
0x11ed3b…2c96
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
2 touches
0 conflicts
0x5b571ba0…f13a
0x368ee5…7ca4
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 0xcdb294d4e0…b7a4e9
Audit this contract →
← previous block·next block →recent activity