← previous blocknext block →recent activity
Analyzing
Block #74,353,610
14 transactions · 10 stateful · 2026-05-13 16:09:50 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,353,610 · 14 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
3w04w18w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x273b6eca…dec3
0x065c9d…c394
2 touches
0 conflicts
0x37a3dc1a…65d0
0x065c9d…c394
2 touches
0 conflicts
0x6f7720db…160d
0x065c9d…c394
2 touches
0 conflicts
0xb0de0dc0…a159
0x065c9d…c394
2 touches
0 conflicts
0xb4f7ffd1…1eca
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity