pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #73,360,563
24 transactions · 19 stateful · 2026-05-09 01:43:25 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,360,563 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w010w011w112w113w114w216w317w418w522w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0xdf5429ce…3c92
0xd32edf…ff58
3 touches
1 conflict
0xbc6f290c…740f
0x065c9d…c394
3 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: 0x2a68ba18…8e90c5
10 conflicts on slot 0xf2f76ab392…f3623e
Audit this contract →
← previous block·next block →recent activity