← previous blocknext block →recent activity
Analyzing
Block #73,672,075
15 transactions · 14 stateful · 2026-05-10 12:20:00 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,672,075 · 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
1w04w15w26w17w38w29w310w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x8a5cfc88…383a
0x065c9d…c394
4 touches
1 conflict
0xc3fa7c6b…5377
0x065c9d…c394
4 touches
1 conflict
0xbc54cf1b…3d05
0x065c9d…c394
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: Market-MON/USDC
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity