← previous blocknext block →recent activity
Analyzing
Block #73,674,019
46 transactions · 40 stateful · 2026-05-10 12:33:11 UTC
Parallelism
78/100
Blocked
70%
Avg conflicts / tx
2.24
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,674,019 · 46 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w08w19w227w328w429w530w631w432w533w734w835w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0x00000000…0002
0xab3526…fa38
14 touches
21 conflicts
0x529acb6a…fcc6
0x065c9d…c394
12 touches
15 conflicts
0xaa8a1c54…ead3
0x34b655…2a6f
12 touches
15 conflicts
0x0ac31945…2c72
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0x3e733ae4…4598
0x34b655…2a6f
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 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
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity