pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,660,544
86 transactions · 65 stateful · 2026-05-10 11:02:11 UTC
Parallelism
84/100
Blocked
78%
Avg conflicts / tx
2.03
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #73,660,544 · 86 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w08w010w111w312w414w116w232w533w335w642w243w764w165w266w367w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xab3526…fa38
20 touches
45 conflicts
0xe6455d1f…1029
0x754704…b603
16 touches
28 conflicts
0x0d0b2509…074d
0x3bd359…433a
16 touches
28 conflicts
0x17606ba6…1b6e
0x754704…b603
14 touches
21 conflicts
0x0d622e34…0000
0x681e90…ae09
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xf2438038…5fa7
0x34b655…2a6f
10 touches
10 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: 0xab35264b…1cfa38
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity