← previous blocknext block →recent activity
Analyzing
Block #81,623,929
13 transactions · 12 stateful · 2026-06-16 08:31:51 UTC
Parallelism
85/100
Blocked
17%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,623,929 · 13 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
1w04w05w110w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce827910…ff22
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7513257f…2749
0x34b655…2a6f
4 touches
1 conflict
0x52e69143…95ad
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x7a12283f…b18a
0x69df8a…6292
2 touches
0 conflicts
0x915c095e…c1e5
0x69df8a…6292
2 touches
0 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
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 0xce827910a4…82ff22
Audit this contract →
← previous block·next block →recent activity