← previous blocknext block →recent activity
Analyzing
Block #76,263,510
21 transactions · 13 stateful · 2026-05-22 12:45:13 UTC
Parallelism
90/100
Blocked
31%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,263,510 · 21 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
1w05w08w19w113w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x8ebf69ec…edcd
0xd45826…f134
4 touches
1 conflict
0x8ebf69ec…edd2
0xd45826…f134
4 touches
1 conflict
0x00000000…0004
0xa7e6f5…bf2c
4 touches
1 conflict
0x00000000…0007
0xa7e6f5…bf2c
4 touches
1 conflict
0x00000000…000b
0xa7e6f5…bf2c
4 touches
1 conflict
0x00000000…00fc
0xd45826…f134
4 touches
1 conflict
0x00000000…0161
0xd45826…f134
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
1 conflict on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity