← previous blocknext block →recent activity
Analyzing
Block #73,417,479
21 transactions · 16 stateful · 2026-05-09 08:02:19 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,417,479 · 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
2w03w17w08w09w110w211w312w413w114w215w320w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xaf498679…7732
0x34b655…2a6f
6 touches
3 conflicts
0xcd5c7f64…ad4b
0x34b655…2a6f
6 touches
3 conflicts
0xd0f6f4f2…dffa
0x34b655…2a6f
6 touches
3 conflicts
0xf6c9bf9b…ac02
0x34b655…2a6f
6 touches
3 conflicts
0xfc139a72…2532
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity