← previous blocknext block →recent activity
Analyzing
Block #74,009,990
9 transactions · 8 stateful · 2026-05-12 02:04:38 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,009,990 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x96e95b9a…4059
0x065c9d…c394
3 touches
1 conflict
0x33697a31…3963
0x1efe02…37d6
2 touches
0 conflicts
0x6ad5b2f5…0e82
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
2 touches
0 conflicts
0x420aa2f2…abe2
0xaa3145…feec
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
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 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity