← previous blocknext block →recent activity
Analyzing
Block #81,480,466
23 transactions · 22 stateful · 2026-06-15 16:36:21 UTC
Parallelism
83/100
Blocked
32%
Avg conflicts / tx
0.39
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #81,480,466 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w29w210w313w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x00000000…0002
0xa976c3…98d1
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
2 touches
1 conflict
0x00000000…0001
0x2c492d…444e
2 touches
0 conflicts
0xa472d565…9fe4
0x3bd359…433a
2 touches
0 conflicts
0xc740dd24…9801
0x3bd359…433a
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity