← previous blocknext block →recent activity
Analyzing
Block #72,973,949
21 transactions · 17 stateful · 2026-05-07 06:51:05 UTC
Parallelism
71/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,973,949 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w38w010w411w514w317w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70b2f813…783c
0x2a68ba…90c5
8 touches
6 conflicts
0x8a014215…f3e3
0xd32edf…ff58
7 touches
6 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5e
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x0a85a226…83c0
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
6 conflicts on slot 0x70b2f81398…04783c
Audit this contract →
← previous block·next block →recent activity