← previous blocknext block →recent activity
Analyzing
Block #74,025,147
6 transactions · 4 stateful · 2026-05-12 03:45:10 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,025,147 · 6 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63498d8…7ca9
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x9e0d9b93…77bb
0x065c9d…c394
3 touches
1 conflict
0xb2e5628c…2a40
0x065c9d…c394
3 touches
1 conflict
0x9a2919d5…60db
0x065c9d…c394
2 touches
0 conflicts
0xde56ca79…1a3d
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
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 0xd63498d831…197ca9
Audit this contract →
← previous block·next block →recent activity