← previous blocknext block →recent activity
Analyzing
Block #74,635,721
8 transactions · 8 stateful · 2026-05-14 23:35:30 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,635,721 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc5178a6a…3dbc
0x065c9d…c394
3 touches
1 conflict
0x504bf28b…6b76
0x065c9d…c394
3 touches
1 conflict
0x761fea0e…29d8
0x065c9d…c394
2 touches
0 conflicts
0xa22d4a11…7c5e
0x065c9d…c394
2 touches
0 conflicts
0xb0ad2353…3356
0x065c9d…c394
2 touches
0 conflicts
0xe317b4fb…995c
0x065c9d…c394
2 touches
0 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
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