← previous blocknext block →recent activity
Analyzing
Block #82,661,067
15 transactions · 13 stateful · 2026-06-21 03:52:47 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,661,067 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xcd642400…9b0a
0x065c9d…c394
4 touches
1 conflict
0x4649eff7…5cc0
0x065c9d…c394
3 touches
1 conflict
0x8582f2f3…84ee
0x065c9d…c394
3 touches
1 conflict
0x0ba2d755…a303
0x40c49f…2af0
2 touches
0 conflicts
0x19b62ad3…7a3c
0x40c49f…2af0
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity