← previous blocknext block →recent activity
Analyzing
Block #77,358,953
21 transactions · 13 stateful · 2026-05-27 14:22:40 UTC
Parallelism
90/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #77,358,953 · 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
1w02w03w14w07w18w09w111w014w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaeb5864c…7679
0x2a68ba…90c5
4 touches
1 conflict
0xc906436c…b676
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x2db6cfa2…15c9
0x40c49f…2af0
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: MarginAccount
1 conflict on slot 0xaeb5864c20…607679
Audit this contract →
← previous block·next block →recent activity