← previous blocknext block →recent activity
Analyzing
Block #74,384,333
14 transactions · 9 stateful · 2026-05-13 19:34:23 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,384,333 · 14 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87003c18…a1ac
0x065c9d…c394
4 touches
1 conflict
0xa2dee4e8…5eff
0x065c9d…c394
4 touches
1 conflict
0x14c5eacd…d50c
0x065c9d…c394
3 touches
1 conflict
0x11fb191a…4360
0x065c9d…c394
3 touches
1 conflict
0x009823fd…4f0d
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x4dd05d17…42eb
0x065c9d…c394
2 touches
0 conflicts
0x6455d074…27c7
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 0x87003c18d4…fca1ac
Audit this contract →
← previous block·next block →recent activity