← previous blocknext block →recent activity
Analyzing
Block #73,036,434
36 transactions · 26 stateful · 2026-05-07 13:47:01 UTC
Parallelism
72/100
Blocked
58%
Avg conflicts / tx
1.17
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,036,434 · 36 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w04w15w26w114w015w116w217w318w419w520w627w129w233w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
14 touches
21 conflicts
0x388e001a…7e04
0x34b655…2a6f
10 touches
10 conflicts
0x161e1ca1…0fd7
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ab
0x8d66a4…3095
7 touches
6 conflicts
0xdaca243a…f9de
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
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