pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,127,809
← previous block
next block →
recent activity
Analyzing
Block #75,127,809
8 transactions · 7 stateful · 2026-05-17 06:21:20 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,127,809
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6c05cd2b
· blocks 1
#3
updateDataFeedsValuesPartial
#4
artefact_keep
#5
0x6a095ed7
#6
setData
#7
0x39435dac
#2
0x6c05cd2b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe161dd…757b
0x3bd359…433a
4 touches
1 conflict
0xd4a0d6d7…df09
0x402807…5159
4 touches
1 conflict
0xb4e825af…69e0
0x3bd359…433a
4 touches
1 conflict
0x24cfe713…0f91
0x25d593…7777
2 touches
0 conflicts
0xd8d48bcb…b81b
0x25d593…7777
2 touches
0 conflicts
0x00000000…0000
0x30611e…d8d9
2 touches
0 conflicts
0x00000000…0001
0x30611e…d8d9
2 touches
0 conflicts
0x00000000…0003
0x30611e…d8d9
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:
Wrapped MON (WMON)
1 conflict on slot
0xfbe161dda4…a6757b
Audit this contract →
← previous block
·
next block →
recent activity