pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#75,902,031
← previous block
next block →
recent activity
Analyzing
Block #75,902,031
9 transactions · 7 stateful · 2026-05-20 20:37:37 UTC
Parallelism
78
/100
Blocked
14
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#75,902,031
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xa96df62f
#2
0x1a945f9c
· blocks 1
#3
0x0f6795d9
#4
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#5
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xac77df1c…44d0
0x1efe02…37d6
2 touches
0 conflicts
0x1be8019f…b769
0x34b655…2a6f
2 touches
0 conflicts
0x1ecc3b8b…5cc3
0xd42a27…01c7
2 touches
0 conflicts
0xb7c3f498…7a8b
0xd42a27…01c7
2 touches
0 conflicts
0xb7c3f498…7a8d
0xd42a27…01c7
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity