← previous blocknext block →recent activity
Analyzing
Block #73,036,304
41 transactions · 35 stateful · 2026-05-07 13:46:09 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
2.83
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #73,036,304 · 41 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w29w210w011w112w213w314w418w019w120w221w322w423w524w625w731w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
26 touches
78 conflicts
0x318ac0bb…6b9c
0x34b655…2a6f
20 touches
45 conflicts
0x20ac0567…c954
0x34b655…2a6f
16 touches
28 conflicts
0x2484cc15…5afc
0x34b655…2a6f
16 touches
28 conflicts
0xac2a0273…721b
0x34b655…2a6f
16 touches
28 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 conflicts
0x6f2e60dc…e661
0x34b655…2a6f
16 touches
28 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
78 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity