← previous blocknext block →recent activity
Analyzing
Block #74,354,538
24 transactions · 17 stateful · 2026-05-13 16:16:02 UTC
Parallelism
92/100
Blocked
41%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,354,538 · 24 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
1w04w05w06w07w111w012w116w118w119w121w123w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaed8e86…b380
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x1d731f70…4557
0x34b655…2a6f
4 touches
1 conflict
0xb079168a…75ea
0x065c9d…c394
4 touches
1 conflict
0x5624a4de…82c6
0xd32edf…ff58
3 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
1 conflict on slot 0xfaed8e8629…82b380
Audit this contract →
← previous block·next block →recent activity