← previous blocknext block →recent activity
Analyzing
Block #73,034,325
19 transactions · 15 stateful · 2026-05-07 13:33:00 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.53
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,034,325 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w210w012w013w114w216w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0x47c1a8e8…f74a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
6 touches
3 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
4 touches
1 conflict
0x17e2d2a0…359e
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x2877f440…c2c8
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
3 conflicts on slot 0x60f7fbaf90…97bd58
Audit this contract →
← previous block·next block →recent activity