← previous blocknext block →recent activity
Analyzing
Block #81,830,335
29 transactions · 21 stateful · 2026-06-17 07:27:07 UTC
Parallelism
83/100
Blocked
57%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,830,335 · 29 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w38w39w412w013w114w215w320w021w122w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0002
0xaa7ee7…f0e4
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 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
6 conflicts on slot 0x160f117d43…518e90
Audit this contract →
← previous block·next block →recent activity