← previous blocknext block →recent activity
Analyzing
Block #73,210,056
15 transactions · 14 stateful · 2026-05-08 09:02:17 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,210,056 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
4 touches
1 conflict
0x3579ab5c…7745
0x065c9d…c394
2 touches
0 conflicts
0x7f189cf6…afab
0x065c9d…c394
2 touches
0 conflicts
0xa6f4fae7…411c
0x065c9d…c394
2 touches
0 conflicts
0xbf7eb941…5468
0x065c9d…c394
2 touches
0 conflicts
0xd6992105…b676
0x065c9d…c394
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity