← previous blocknext block →recent activity
Analyzing
Block #73,042,304
14 transactions · 13 stateful · 2026-05-07 14:26:04 UTC
Parallelism
64/100
Blocked
46%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,042,304 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w07w19w210w311w413w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7bfe5e…5e58
0x065c9d…c394
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xf4730a2d…3538
0x34b655…2a6f
4 touches
1 conflict
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
2 touches
0 conflicts
0x1a4b4152…0a08
0x6ca43f…c331
2 touches
0 conflicts
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: Market-MON/USDC
10 conflicts on slot 0xce7bfe5ef1…205e58
Audit this contract →
← previous block·next block →recent activity