← previous blocknext block →recent activity
Analyzing
Block #75,097,640
9 transactions · 8 stateful · 2026-05-17 02:59:59 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,097,640 · 9 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
1w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x630e3425…1dcf
0x065c9d…c394
4 touches
1 conflict
0xe847e1cc…3f63
0x065c9d…c394
3 touches
1 conflict
0xf6cc3cc7…49e0
0x065c9d…c394
3 touches
1 conflict
0x2a0ddd10…9cc2
0x065c9d…c394
3 touches
1 conflict
0x31580f33…a833
0x065c9d…c394
3 touches
1 conflict
0x7114b41e…5ae8
0x065c9d…c394
2 touches
0 conflicts
0xcf69ea22…40db
0x065c9d…c394
2 touches
0 conflicts
0xdb84c3ed…1866
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 0x630e3425d3…651dcf
Audit this contract →
← previous block·next block →recent activity