pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,924,465
← previous block
next block →
recent activity
Analyzing
Block #75,924,465
10 transactions · 7 stateful · 2026-05-20 23:06:56 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,924,465
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x98717539
#3
updateDataFeedsValuesPartial
#4
0x4e1a89…c981
#5
0x475c01…51e6
#6
setData
#7
0x39435dac
· blocks 1
#8
0x39435dac
#9
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9210f658…c808
0x34b655…2a6f
4 touches
1 conflict
0xc7f28b7a…5777
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2ecef33c…104f
0x065c9d…c394
2 touches
0 conflicts
0x3027c19c…b5a1
0x065c9d…c394
2 touches
0 conflicts
0x4107325c…ffb9
0x065c9d…c394
2 touches
0 conflicts
0x5f77d607…2c84
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:
Perpl
1 conflict on slot
0x9210f658a2…fcc808
Audit this contract →
← previous block
·
next block →
recent activity