← previous blocknext block →recent activity
Analyzing
Block #82,223,905
14 transactions · 12 stateful · 2026-06-19 03:13:03 UTC
Parallelism
79/100
Blocked
17%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,223,905 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x660dd3f1…6bcc
0x065c9d…c394
3 touches
1 conflict
0xb7f806ff…845e
0x065c9d…c394
3 touches
1 conflict
0x64725866…b55c
0x065c9d…c394
2 touches
0 conflicts
0x8e82d96f…c326
0x065c9d…c394
2 touches
0 conflicts
0x99a91259…03ef
0x065c9d…c394
2 touches
0 conflicts
0x9fc936a6…f1f9
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