← previous blocknext block →recent activity
Analyzing
Block #82,683,990
16 transactions · 12 stateful · 2026-06-21 06:26:13 UTC
Parallelism
63/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,683,990 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x557cd4fa…228c
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x994e984d…bc23
0x065c9d…c394
3 touches
1 conflict
0xa831987e…a6f7
0x065c9d…c394
3 touches
1 conflict
0xacb3fde4…82db
0x065c9d…c394
3 touches
1 conflict
0x0f091be6…b684
0x065c9d…c394
3 touches
1 conflict
0x915a3b9f…6d69
0x065c9d…c394
3 touches
1 conflict
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity