pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#73,501,182
← previous block
next block →
recent activity
Analyzing
Block #73,501,182
8 transactions · 7 stateful · 2026-05-09 17:19:15 UTC
Parallelism
50
/100
Blocked
43
%
Avg conflicts / tx
0.75
Longest chain
4
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,501,182
· 8 txs across 4 waves · depth 4
parallel ↔ serial
wave
w0
wave
w1
wave
w2
wave
w3
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
setData
#3
0x6df9e92b
· blocks 3
#7
0x69ff6d0b
#4
0x6df9e92b
· blocks 2
#5
0x6df9e92b
· blocks 1
#6
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
6
w3
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b144217…a58e
0xb68427…7777
8 touches
6 conflicts
0x00000000…0001
0x3704e4…e36f
8 touches
6 conflicts
0xa472d565…9fe4
0x3bd359…433a
8 touches
6 conflicts
0xea8e8e68…ba34
0x3bd359…433a
8 touches
6 conflicts
0x44ad89ba…cf83
0xb68427…7777
8 touches
6 conflicts
0x00000000…0000
0x3704e4…e36f
8 touches
6 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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:
0xb6842737…e87777
6 conflicts on slot
0x8b14421719…26a58e
Audit this contract →
← previous block
·
next block →
recent activity