← previous blocknext block →recent activity
Analyzing
Block #73,696,887
23 transactions · 21 stateful · 2026-05-10 15:07:25 UTC
Parallelism
61/100
Blocked
62%
Avg conflicts / tx
2.22
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,696,887 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w010w113w114w215w116w217w318w419w520w621w722w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
16 touches
28 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0x529acb6a…fcc6
0x065c9d…c394
10 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x3c2e35d5…b375
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
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
28 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity