← previous blocknext block →recent activity
Analyzing
Block #75,697,487
12 transactions · 8 stateful · 2026-05-19 21:54:04 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,697,487 · 12 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
2w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf70c44e5…cccf
0x065c9d…c394
4 touches
1 conflict
0x36f0dad5…ac05
0x065c9d…c394
3 touches
1 conflict
0x050d7902…1f67
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x168e3d0c…6fdb
0x065c9d…c394
2 touches
0 conflicts
0x1db1dadb…ca7d
0x065c9d…c394
2 touches
0 conflicts
0xaa2d2260…8f5d
0x065c9d…c394
2 touches
0 conflicts
0xcc4f1f14…aa5f
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
1 conflict on slot 0xf70c44e505…fdcccf
Audit this contract →
← previous block·next block →recent activity