← previous blocknext block →recent activity
Analyzing
Block #81,480,069
17 transactions · 12 stateful · 2026-06-15 16:33:42 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,480,069 · 17 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
2w03w04w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19c415d3…1cd9
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0xacdf56b3…e33c
0xa6afd3…d132
4 touches
1 conflict
0x2fb6ddd2…b2a4
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x38eaa2ec…da63
0x188d58…ea8e
2 touches
0 conflicts
0x38eaa2ec…da64
0x188d58…ea8e
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 0x19c415d316…1f1cd9
Audit this contract →
← previous block·next block →recent activity