← previous blocknext block →recent activity
Analyzing
Block #73,981,128
7 transactions · 5 stateful · 2026-05-11 22:50:20 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,981,128 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0ddbfd1d…93dd
0x065c9d…c394
2 touches
0 conflicts
0x610cc3a1…dae5
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x7e1c96e5…a8e5
0x065c9d…c394
2 touches
0 conflicts
0xc48d8515…98b0
0x065c9d…c394
2 touches
0 conflicts
0xcc6297d6…76bb
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
1 conflict on slot 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity