← previous blocknext block →recent activity
Analyzing
Block #73,743,912
18 transactions · 17 stateful · 2026-05-10 20:24:49 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.39
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,743,912 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w111w012w113w214w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0x614b85…a284
2 touches
0 conflicts
0x00000000…0003
0x614b85…a284
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
3 conflicts on slot 0x529acb6ad1…f0fcc6
Audit this contract →
← previous block·next block →recent activity