← previous blocknext block →recent activity
Analyzing
Block #73,918,300
10 transactions · 8 stateful · 2026-05-11 15:51:38 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,918,300 · 10 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
1w02w15w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x742436a7…c4d4
0x34b655…2a6f
4 touches
1 conflict
0x04c14a40…b1ac
0x065c9d…c394
2 touches
0 conflicts
0x30869256…c9d7
0x065c9d…c394
2 touches
0 conflicts
0x416e2742…b455
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0xa3428a2b…bed7
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity