pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#73,358,473
← previous block
next block →
recent activity
Analyzing
Block #73,358,473
8 transactions · 8 stateful · 2026-05-09 01:29:33 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#73,358,473
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
updateDataFeedsValuesPartial
#3
0xeffdedb0
#4
setData
#5
0x39435dac
· blocks 1
#7
0x39435dac
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee576a92…fe14
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x0462262d…a368
0x34b655…2a6f
2 touches
0 conflicts
0x445b51c5…0be4
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x6713b018…05f3
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xee576a924c…75fe14
Audit this contract →
← previous block
·
next block →
recent activity