← previous blocknext block →recent activity
Analyzing
Block #73,035,883
16 transactions · 16 stateful · 2026-05-07 13:43:21 UTC
Parallelism
50/100
Blocked
44%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,035,883 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x388e001a…7e04
0x34b655…2a6f
14 touches
21 conflicts
0x65b89141…61de
0x34b655…2a6f
10 touches
10 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
10 touches
10 conflicts
0xc6417de0…2191
0xc8689a…ee79
8 touches
6 conflicts
0x0b28bf77…e53a
0x34b655…2a6f
8 touches
6 conflicts
0x32ee90db…decc
0x34b655…2a6f
8 touches
6 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
8 touches
6 conflicts
0x9cc607d0…c9c7
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