← previous blocknext block →recent activity
Analyzing
Block #73,846,041
19 transactions · 18 stateful · 2026-05-11 07:49:59 UTC
Parallelism
58/100
Blocked
61%
Avg conflicts / tx
2.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,846,041 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w29w310w111w212w313w414w515w616w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x22e295f5…1bef
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x735758e7…e7e2
0x065c9d…c394
6 touches
3 conflicts
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x8fcbbd35…bf07
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity