← previous blocknext block →recent activity
Analyzing
Block #73,036,339
23 transactions · 19 stateful · 2026-05-07 13:46:23 UTC
Parallelism
78/100
Blocked
47%
Avg conflicts / tx
0.91
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,036,339 · 23 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
5w06w17w28w39w412w013w114w215w316w421w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x161e1ca1…0fd7
0x34b655…2a6f
8 touches
6 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
8 touches
6 conflicts
0x32ee90db…decc
0x34b655…2a6f
8 touches
6 conflicts
0x388e001a…7e04
0x34b655…2a6f
8 touches
6 conflicts
0x65b89141…61de
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 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: 0xd574cae5…037ab1
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity