← previous blocknext block →recent activity
Analyzing
Block #82,193,422
12 transactions · 11 stateful · 2026-06-18 23:50:00 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,193,422 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfb2516a4…0026
0x065c9d…c394
4 touches
1 conflict
0x204c969e…25c5
0x065c9d…c394
3 touches
1 conflict
0x6fdc81bc…0f02
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0c282cfa…95af
0x065c9d…c394
2 touches
0 conflicts
0x3f59131a…fa87
0x065c9d…c394
2 touches
0 conflicts
0xca4542ce…bdb2
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 0xfb2516a445…250026
Audit this contract →
← previous block·next block →recent activity