pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#75,525,766
← previous block
next block →
recent activity
Analyzing
Block #75,525,766
10 transactions · 7 stateful · 2026-05-19 02:48:58 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,525,766
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
· blocks 1
#2
updateDataFeedsValuesPartial
#3
0x6a0bd011
#4
setData
#5
0x2eefc9…730d
#6
0xd84d1b…d4a9
#8
0x39435dac
#9
0x39435dac
#7
metacall
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x21c137b8…3a77
0x3bd359…433a
4 touches
1 conflict
0xd4a0d6d7…df09
0x402807…5159
4 touches
1 conflict
0x00000000…0008
0x509771…3c7b
4 touches
1 conflict
0x4d394876…c488
0x402807…5159
4 touches
1 conflict
0xb4e825af…69e0
0x3bd359…433a
2 touches
0 conflicts
0xfbe161dd…757b
0x3bd359…433a
2 touches
0 conflicts
0xcd25bd8f…0a6a
0x402807…5159
2 touches
0 conflicts
0x00000000…0009
0x509771…3c7b
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:
0x3bd359c1…15433a
1 conflict on slot
0x21c137b850…5d3a77
Audit this contract →
← previous block
·
next block →
recent activity