← previous blocknext block →recent activity
Analyzing
Block #73,038,313
13 transactions · 12 stateful · 2026-05-07 13:59:31 UTC
Parallelism
31/100
Blocked
67%
Avg conflicts / tx
2.23
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #73,038,313 · 13 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w510w611w712w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
14 touches
21 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0x32ee90db…decc
0x34b655…2a6f
8 touches
6 conflicts
0x3638e1ad…ec0e
0x34b655…2a6f
8 touches
6 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x23951077…539b
0x34b655…2a6f
8 touches
6 conflicts
0x5aeaf08b…cbf7
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: Perpl
21 conflicts on slot 0x388e001a16…e57e04
Audit this contract →
← previous block·next block →recent activity