← previous blocknext block →recent activity
Analyzing
Block #74,538,525
28 transactions · 16 stateful · 2026-05-14 12:43:48 UTC
Parallelism
79/100
Blocked
44%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #74,538,525 · 28 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w310w011w121w422w023w526w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x41755291…977f
0x065c9d…c394
6 touches
3 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
6 touches
3 conflicts
0x791c3843…3f61
0x065c9d…c394
4 touches
2 conflicts
0x6b319071…a105
0xc8689a…ee79
4 touches
1 conflict
0x32c48a7e…5028
0x065c9d…c394
4 touches
1 conflict
0x0175b7a6…1dba
0x5d823e…89c6
4 touches
1 conflict
0x0175b7a6…1dbb
0x5d823e…89c6
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity