← previous blocknext block →recent activity
Analyzing
Block #73,036,154
22 transactions · 19 stateful · 2026-05-07 13:45:09 UTC
Parallelism
68/100
Blocked
42%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,036,154 · 22 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
2w03w17w08w19w210w311w412w513w620w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
7 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 touches
3 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
6 touches
3 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
6 touches
3 conflicts
0x32ee90db…decc
0x34b655…2a6f
6 touches
3 conflicts
0x388e001a…7e04
0x34b655…2a6f
6 touches
3 conflicts
0x65b89141…61de
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
21 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity