← previous blocknext block →recent activity
Analyzing
Block #73,187,958
25 transactions · 20 stateful · 2026-05-08 06:35:14 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.08
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,187,958 · 25 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
1w04w17w08w112w215w316w417w518w619w420w721w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8e66da19…66b6
0x065c9d…c394
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xa655bf35…da0a
0xd32edf…ff58
7 touches
6 conflicts
0x2a354a63…0515
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0xcdfa9756…ab1c
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
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
10 conflicts on slot 0x8e66da1932…c966b6
Audit this contract →
← previous block·next block →recent activity