← previous blocknext block →recent activity
Analyzing
Block #73,496,728
38 transactions · 33 stateful · 2026-05-09 16:49:35 UTC
Parallelism
50/100
Blocked
73%
Avg conflicts / tx
3.84
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #73,496,728 · 38 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w19w210w311w412w513w614w715w816w917w1018w1119w1221w1322w1423w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
32 touches
120 conflicts
0xa91c899f…6ee3
0x34b655…2a6f
30 touches
105 conflicts
0xedb848fe…6534
0x34b655…2a6f
30 touches
105 conflicts
0x23951077…539b
0x34b655…2a6f
28 touches
91 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
28 touches
91 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
28 touches
91 conflicts
0xc6417de0…2191
0xc8689a…ee79
28 touches
91 conflicts
0x1acaa26f…7b77
0x34b655…2a6f
28 touches
91 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
120 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity