← previous blocknext block →recent activity
Analyzing
Block #75,523,127
19 transactions · 10 stateful · 2026-05-19 02:30:55 UTC
Parallelism
89/100
Blocked
20%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,523,127 · 19 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
2w03w17w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8cd3960d…0abe
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xf6d5644f…b9f7
0x1efe02…37d6
2 touches
0 conflicts
0x00bac013…a28c
0x91b81b…6d56
2 touches
0 conflicts
0x9560013d…8caf
0x91b81b…6d56
2 touches
0 conflicts
0x5c0c0e2c…7116
0xd42a27…01c7
2 touches
0 conflicts
0x03d5e9ea…40ad
0xea1b8e…c5ec
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity