pev.One block, wave by wave
analyticsdocsfeedback
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #74,306,628
16 transactions · 15 stateful · 2026-05-13 10:57:28 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #74,306,628 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w18w210w211w312w413w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fc5fab2…880b
0xd32edf…ff58
9 touches
10 conflicts
0xce8bbe33…b72e
0x3bd359…433a
8 touches
6 conflicts
0x6af306bb…2e81
0x3bd359…433a
8 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x46cb45de…a567
0x188d58…ea8e
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
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: 0xd32edf66…9fff58
10 conflicts on slot 0x2fc5fab292…1c880b
Audit this contract →
← previous block·next block →recent activity