← previous blocknext block →recent activity
Analyzing
Block #73,642,881
33 transactions · 31 stateful · 2026-05-10 09:03:13 UTC
Parallelism
48/100
Blocked
65%
Avg conflicts / tx
4.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #73,642,881 · 33 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w07w18w19w210w311w412w513w614w715w816w917w1018w1119w1220w1325w226w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5de96bd3…c60c
0x34b655…2a6f
32 touches
120 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
28 touches
91 conflicts
0xc6417de0…2191
0xc8689a…ee79
26 touches
78 conflicts
0xedb848fe…6534
0x34b655…2a6f
26 touches
78 conflicts
0x57de3828…3fbb
0x34b655…2a6f
26 touches
78 conflicts
0x99120c08…ee84
0x34b655…2a6f
24 touches
66 conflicts
0x6eba5e7f…4b52
0x34b655…2a6f
24 touches
66 conflicts
0x1b9e654e…0a08
0x34b655…2a6f
22 touches
55 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
120 conflicts on slot 0x5de96bd34a…ecc60c
Audit this contract →
← previous block·next block →recent activity