pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,099,581
16 transactions · 15 stateful · 2026-05-03 05:38:39 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,099,581 · 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
1w02w13w04w15w26w07w18w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1423ffb0…0900
0xd32edf…ff58
7 touches
6 conflicts
0xce8bbe33…b72e
0x3bd359…433a
6 touches
3 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0x7e9d3a…9fda
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0xbcb0a03b…f65a
0x065c9d…c394
3 touches
1 conflict
0x09000000…0001
0x000000…1000
2 touches
0 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: 0xd32edf66…9fff58
6 conflicts on slot 0x1423ffb0c8…b00900
Audit this contract →
← previous block·next block →recent activity