← previous blocknext block →recent activity
Analyzing
Block #74,775,528
20 transactions · 14 stateful · 2026-05-15 15:09:03 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #74,775,528 · 20 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
1w08w09w112w114w215w319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3e49348b…9445
0x34b655…2a6f
6 touches
3 conflicts
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x35b65947…44d1
0xc8689a…ee79
4 touches
1 conflict
0x8aa1941d…2988
0x34b655…2a6f
4 touches
1 conflict
0xafbd7482…1895
0x34b655…2a6f
4 touches
1 conflict
0xc7965d53…eb99
0x34b655…2a6f
4 touches
1 conflict
0xd504d431…1394
0x34b655…2a6f
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