← previous blocknext block →recent activity
Analyzing
Block #74,026,147
8 transactions · 6 stateful · 2026-05-12 03:51:50 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,026,147 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x874d2ef6…9b06
0x065c9d…c394
3 touches
1 conflict
0x238b51ac…dd1c
0x065c9d…c394
2 touches
0 conflicts
0x284f1de9…3525
0x065c9d…c394
2 touches
0 conflicts
0x2fda6a97…e778
0x065c9d…c394
2 touches
0 conflicts
0x38d6f60f…2d9f
0x065c9d…c394
2 touches
0 conflicts
0x39b85263…3cd4
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 0xbd7e37a9b5…859eb5
Audit this contract →
← previous block·next block →recent activity