← previous blocknext block →recent activity
Analyzing
Block #81,876,807
13 transactions · 10 stateful · 2026-06-17 12:36:49 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #81,876,807 · 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
1w02w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c560f0b…4359
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xe91a4e7d…5dc1
0x699abc…6a3b
4 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
4 touches
1 conflict
0x4b292c6e…6051
0x699abc…6a3b
4 touches
1 conflict
0xef65bff3…7c9d
0x2a68ba…90c5
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x95f19fd2…daf0
0xa6afd3…d132
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
1 conflict on slot 0x5c560f0bc7…314359
Audit this contract →
← previous block·next block →recent activity