pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,855,962
42 transactions · 35 stateful · 2026-05-06 17:45:53 UTC
Parallelism
69/100
Blocked
69%
Avg conflicts / tx
2
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #72,855,962 · 42 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
1w02w05w18w09w110w211w114w315w216w219w329w631w732w833w934w1035w1136w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
18 touches
36 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
14 touches
21 conflicts
0xf4730a2d…3538
0x34b655…2a6f
12 touches
15 conflicts
0x7f189cf6…afab
0x065c9d…c394
10 touches
10 conflicts
0x5490b6b7…f5a8
0xd32edf…ff58
9 touches
10 conflicts
0x0eac6378…36f4
0x34b655…2a6f
8 touches
6 conflicts
0x150af51d…9c42
0x34b655…2a6f
8 touches
6 conflicts
0x3c35979a…975d
0x34b655…2a6f
8 touches
6 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: 0x065c9d28…a9c394
36 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity