← previous blocknext block →recent activity
Analyzing
Block #82,267,400
11 transactions · 11 stateful · 2026-06-19 08:03:21 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #82,267,400 · 11 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
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba5a2489…76a7
0x065c9d…c394
4 touches
1 conflict
0x89f71bd4…b01e
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x21bc577a…8d4c
0x065c9d…c394
2 touches
0 conflicts
0x5f1f219a…a28c
0x065c9d…c394
2 touches
0 conflicts
0x6b8d5e1f…be83
0x065c9d…c394
2 touches
0 conflicts
0xd4fe4c4e…900d
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 0xba5a248974…3976a7
Audit this contract →
← previous block·next block →recent activity