pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,444,382
← previous block
next block →
recent activity
Analyzing
Block #76,444,382
9 transactions · 8 stateful · 2026-05-23 08:49:35 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,444,382
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xed82b078
· blocks 1
#2
0x5339c59f
· blocks 1
#4
updateDataFeedsValuesPartial
#5
0x85367786
· blocks 1
#7
setData
#8
0x39435dac
#3
0xed82b078
#6
0x85367786
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w0
3
w1
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x247d3d81…6084
0x2c4667…b389
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0xb0e249e9…705d
0x2c4667…b389
2 touches
0 conflicts
0xf313474a…47e3
0x2c4667…b389
2 touches
0 conflicts
0x09106a95…1467
0x33176b…e078
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:
0x2c466769…99b389
1 conflict on slot
0x247d3d814d…366084
Audit this contract →
← previous block
·
next block →
recent activity