← previous blocknext block →recent activity
Analyzing
Block #73,752,022
14 transactions · 12 stateful · 2026-05-10 21:19:35 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,752,022 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w08w19w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xe429e4c9…9510
0x34b655…2a6f
8 touches
6 conflicts
0x94a3fb3f…7515
0x34b655…2a6f
6 touches
3 conflicts
0x59ef13ba…2741
0x34b655…2a6f
6 touches
3 conflicts
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x3b9e61ad…a20d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity