← previous blocknext block →recent activity
Analyzing
Block #82,641,632
7 transactions · 5 stateful · 2026-06-21 01:42:24 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,641,632 · 7 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb9c1cf0e…6b61
0x065c9d…c394
4 touches
1 conflict
0x5e555ef3…43d8
0x065c9d…c394
3 touches
1 conflict
0xb2f3255d…0d20
0x065c9d…c394
3 touches
1 conflict
0x489d031a…407d
0x065c9d…c394
2 touches
0 conflicts
0x5540f956…69e8
0x065c9d…c394
2 touches
0 conflicts
0x7d3ae06a…c716
0x065c9d…c394
2 touches
0 conflicts
0xa17785ac…4302
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