← previous blocknext block →recent activity
Analyzing
Block #81,480,682
21 transactions · 19 stateful · 2026-06-15 16:37:47 UTC
Parallelism
76/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,480,682 · 21 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
1w02w03w14w05w06w17w29w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x73131ffc…b46c
0x5df178…7777
6 touches
3 conflicts
0x44ad89ba…cf83
0x5df178…7777
6 touches
3 conflicts
0xc740dd24…9801
0x3bd359…433a
6 touches
3 conflicts
0xa472d565…9fe4
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0001
0x2c492d…444e
6 touches
3 conflicts
0x00000000…0000
0x2c492d…444e
6 touches
3 conflicts
0xacdf56b3…e33c
0xa6afd3…d132
4 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: MarginAccount
6 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity