pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,910,546
← previous block
next block →
recent activity
Analyzing
Block #75,910,546
10 transactions · 9 stateful · 2026-05-20 21:34:19 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,910,546
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
#2
updateDataFeedsValuesPartial
#3
updateDataFeedsValuesPartial
#4
0x5bf9264c
#5
0x5bf9264c
#6
setData
#7
0xd10227eb
· blocks 1
#9
forward
#8
closeTrade
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4a0d05b1…1c9e
0xea1b8e…c5ec
3 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x97454a76…0ab6
0x065c9d…c394
2 touches
0 conflicts
0x9e9bf66f…68bb
0x065c9d…c394
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x9bf064a6…4f04
0x2a68ba…90c5
2 touches
0 conflicts
0x22e0cc1d…ad04
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:
LeverUp: LeverUp
1 conflict on slot
0x4a0d05b108…081c9e
Audit this contract →
← previous block
·
next block →
recent activity