pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,433,980
← previous block
next block →
recent activity
Analyzing
Block #74,433,980
8 transactions · 6 stateful · 2026-05-14 01:04:54 UTC
Parallelism
75
/100
Blocked
17
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,433,980
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0xed82b078
#3
updateDataFeedsValuesPartial
#4
0x98717539
· blocks 1
#5
setData
#7
jMMeC
#6
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0x48b5b530…b4c5
0x065c9d…c394
2 touches
0 conflicts
0x65296388…ae77
0x065c9d…c394
2 touches
0 conflicts
0x7789a4be…5bbb
0x065c9d…c394
2 touches
0 conflicts
0x8a8678b8…384a
0x065c9d…c394
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:
Perpl
1 conflict on slot
0x2877f4400c…13c2c8
Audit this contract →
← previous block
·
next block →
recent activity