pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,046,875
← previous block
next block →
recent activity
Analyzing
Block #75,046,875
7 transactions · 6 stateful · 2026-05-16 21:21:18 UTC
Parallelism
71
/100
Blocked
33
%
Avg conflicts / tx
0.29
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,046,875
· 7 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x39ecce49
· blocks 1
#3
updateDataFeedsValuesPartial
#4
0xed82b078
· blocks 1
#6
setData
#2
0x39ecce49
#5
0xed82b078
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x30611e…d8d9
4 touches
1 conflict
0x00000000…0003
0x30611e…d8d9
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24cfe713…0f91
0x25d593…7777
4 touches
1 conflict
0x00000000…0000
0x30611e…d8d9
4 touches
1 conflict
0xe3ee7f9e…f356
0x3bd359…433a
4 touches
1 conflict
0x49fb365e…c494
0x25d593…7777
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
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:
0x30611e93…1ad8d9
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity