← previous blocknext block →recent activity
Analyzing
Block #75,485,195
19 transactions · 16 stateful · 2026-05-18 22:11:00 UTC
Parallelism
79/100
Blocked
38%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,485,195 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w07w18w09w111w012w215w316w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0x63e48b…53f2
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x8d66a4…3095
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x0711ec2d…d973
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity