← previous blocknext block →recent activity
Analyzing
Block #82,174,125
13 transactions · 13 stateful · 2026-06-18 21:41:25 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,174,125 · 13 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
1w02w03w14w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x85631114…3ff6
0xa6afd3…d132
4 touches
1 conflict
0x29014292…f798
0x065c9d…c394
2 touches
0 conflicts
0x49898b74…8f5d
0x065c9d…c394
2 touches
0 conflicts
0x92b6c3a0…457b
0x065c9d…c394
2 touches
0 conflicts
0x99029136…0eb7
0x065c9d…c394
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