← previous blocknext block →recent activity
Analyzing
Block #72,398,970
16 transactions · 14 stateful · 2026-05-04 15:00:21 UTC
Parallelism
63/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,398,970 · 16 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
1w03w15w06w17w28w311w312w413w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92d610a6…9a40
0x2a68ba…90c5
10 touches
10 conflicts
0xf38c8dfe…52ca
0x065c9d…c394
9 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x7eeb9792…3604
0xc8689a…ee79
4 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xbf04f37d…85f2
0x2a68ba…90c5
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
10 conflicts on slot 0x92d610a6f9…379a40
Audit this contract →
← previous block·next block →recent activity