pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#71,741,486
← previous block
next block →
recent activity
Analyzing
Block #71,741,486
12 transactions · 10 stateful · 2026-05-01 13:54:38 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#71,741,486
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
safeTransferFrom
#2
0xeffdedb0
#3
updateDataFeedsValuesPartial
#4
withdraw
#5
0x3f5c179b
#6
0xd10227eb
#7
swap
#8
forward
#9
setData
#10
0x39435dac
· blocks 1
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xc03a03cd…fbcf
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x92339d95…0800
0x0000a8…8888
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x00a4ce9b…d869
0x065c9d…c394
2 touches
0 conflicts
0x0aebd6a7…f0e0
0x065c9d…c394
2 touches
0 conflicts
0x38207428…8830
0x065c9d…c394
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:
0x34b6552d…112a6f
1 conflict on slot
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity