← previous blocknext block →recent activity
Analyzing
Block #73,324,657
17 transactions · 14 stateful · 2026-05-08 21:44:43 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.35
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,324,657 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w19w210w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbd7e37a9…9eb5
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x4f91fd62…d68e
0x065c9d…c394
4 touches
1 conflict
0x81d2e592…76e1
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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
15 conflicts on slot 0x046a928e85…e50012
Audit this contract →
← previous block·next block →recent activity