← previous blocknext block →recent activity
Analyzing
Block #73,807,813
11 transactions · 9 stateful · 2026-05-11 03:35:36 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,807,813 · 11 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
1w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x58e1721b…c52d
0x065c9d…c394
4 touches
1 conflict
0x848a7dc9…9e95
0x065c9d…c394
3 touches
1 conflict
0x2a0ce634…2985
0x065c9d…c394
3 touches
1 conflict
0x3b788ca7…dd14
0x065c9d…c394
2 touches
0 conflicts
0x3b9dae27…a0b8
0x065c9d…c394
2 touches
0 conflicts
0x450adf0b…cf23
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity