← previous blocknext block →recent activity
Analyzing
Block #73,187,916
14 transactions · 14 stateful · 2026-05-08 06:34:57 UTC
Parallelism
50/100
Blocked
64%
Avg conflicts / tx
1.86
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,187,916 · 14 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
1w02w13w26w37w38w49w410w511w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x2a354a63…0515
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xb9ef2a6d…254f
0x065c9d…c394
4 touches
1 conflict
0x3301e294…30a0
0x065c9d…c394
4 touches
1 conflict
0x5c9c9e90…dac4
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity