pev
.
One block, wave by wave
→
analytics
docs
offline
by Silk Nodes →
pev
/
block
/
#74,188,275
← previous block
next block →
recent activity
Analyzing
Block #74,188,275
13 transactions · 9 stateful · 2026-05-12 21:50:20 UTC
Parallelism
85
/100
Blocked
11
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,188,275
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ffa3c9b
#2
0x39abec6b
#3
0x0f6795d9
#4
0x6df9e92b
· blocks 1
#6
updateDataFeedsValuesPartial
#7
handleOps
#8
setData
#9
0x43e848…8d13
#10
0x1c020a…038a
#11
0x2858eb…402c
#12
0x39435dac
#5
0x6df9e92b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9b1a47c3…69f8
0xde22b2…7777
4 touches
1 conflict
0xa472d565…9fe4
0x3bd359…433a
4 touches
1 conflict
0xbf25e763…684f
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x776059…1d8d
4 touches
1 conflict
0x00000000…0001
0x776059…1d8d
4 touches
1 conflict
0x44ad89ba…cf83
0xde22b2…7777
4 touches
1 conflict
0xc74539a2…ec73
0x065c9d…c394
2 touches
0 conflicts
0xcf652486…8323
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:
0xde22b2d5…9f7777
1 conflict on slot
0x9b1a47c3d7…c169f8
Audit this contract →
← previous block
·
next block →
recent activity