← previous blocknext block →recent activity
Analyzing
Block #74,024,549
18 transactions · 16 stateful · 2026-05-12 03:41:12 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
1.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #74,024,549 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w07w412w513w614w715w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x446e13b9…4a1e
0xd32edf…ff58
7 touches
6 conflicts
0xe783dfa4…5496
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xd1217ea0…2246
0x065c9d…c394
5 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity