← previous blocknext block →recent activity
Analyzing
Block #73,477,382
20 transactions · 19 stateful · 2026-05-09 14:40:49 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
1.65
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,477,382 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w014w015w116w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0003
0x37b81d…17d7
14 touches
21 conflicts
0x3b23d356…dcda
0x3bd359…433a
14 touches
21 conflicts
0x551f6273…7c20
0x42a4aa…7777
14 touches
21 conflicts
0x00000000…0000
0x37b81d…17d7
14 touches
21 conflicts
0x00000000…0001
0x37b81d…17d7
14 touches
21 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 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: 0x37b81dc0…2e17d7
21 conflicts on slot 0x0000000000…000003
Audit this contract →
← previous block·next block →recent activity