← previous blocknext block →recent activity
Analyzing
Block #74,333,164
21 transactions · 15 stateful · 2026-05-13 13:53:55 UTC
Parallelism
86/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,333,164 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w09w010w112w113w215w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xea02471d…1539
0x34b655…2a6f
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x6946d7b5…3c0d
0x065c9d…c394
2 touches
0 conflicts
0x6d8249e8…fc37
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity