← previous blocknext block →recent activity
Analyzing
Block #75,506,507
8 transactions · 7 stateful · 2026-05-19 00:37:07 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,506,507 · 8 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
2w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xb99da793…b905
0x065c9d…c394
3 touches
1 conflict
0xb59488ea…39ce
0x065c9d…c394
3 touches
1 conflict
0x5aa7ecb2…415b
0x065c9d…c394
2 touches
0 conflicts
0x66000db1…da21
0x065c9d…c394
2 touches
0 conflicts
0xe821b807…c6f0
0x065c9d…c394
2 touches
0 conflicts
0x11d4dcaa…0d6a
0x1d1325…2305
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