← previous blocknext block →recent activity
Analyzing
Block #73,479,325
21 transactions · 18 stateful · 2026-05-09 14:53:46 UTC
Parallelism
76/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,479,325 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w16w17w18w29w315w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x67d1be…196f
8 touches
6 conflicts
0x2b936aa5…05e5
0x141b1d…9583
8 touches
6 conflicts
0x00000000…0003
0x2ae0cf…3d4e
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xd84d1890…cd9e
0x065c9d…c394
4 touches
1 conflict
0x4dd1db39…a994
0x188d58…ea8e
4 touches
1 conflict
0x4dd1db39…a996
0x188d58…ea8e
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: 0x67d1be51…42196f
6 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity