← previous blocknext block →recent activity
Analyzing
Block #73,386,473
8 transactions · 7 stateful · 2026-05-09 04:35:50 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,386,473 · 8 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
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd0fa96…5d6b
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xd11aa823…9d29
0x065c9d…c394
3 touches
1 conflict
0xe0e4fd6f…2574
0x065c9d…c394
3 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x719bb1e1…bd5a
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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
1 conflict on slot 0xfcd0fa961f…b65d6b
Audit this contract →
← previous block·next block →recent activity