← previous blocknext block →recent activity
Analyzing
Block #73,798,938
15 transactions · 15 stateful · 2026-05-11 02:36:05 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.8
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,798,938 · 15 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
1w02w04w15w26w38w29w410w511w614w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0xb159af88…a9e7
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0x38524fae…9deb
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xba6473b4…5144
0x065c9d…c394
3 touches
1 conflict
0xf6546231…54ff
0x065c9d…c394
3 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: Market-MON/USDC
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity