← previous blocknext block →recent activity
Analyzing
Block #74,480,935
11 transactions · 11 stateful · 2026-05-14 06:17:21 UTC
Parallelism
73/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,480,935 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xab46ab52…e609
0x065c9d…c394
4 touches
1 conflict
0x81ab0ccf…a21f
0x065c9d…c394
3 touches
1 conflict
0xadb6d34e…cc1c
0x065c9d…c394
3 touches
1 conflict
0x15f56068…625d
0x065c9d…c394
2 touches
0 conflicts
0x443ea66b…011d
0x065c9d…c394
2 touches
0 conflicts
0x545e7eb0…1d68
0x065c9d…c394
2 touches
0 conflicts
0x871b2fea…8767
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity