pev
.
One block, wave by wave
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,421,128
← previous block
next block →
recent activity
Analyzing
Block #74,421,128
15 transactions · 7 stateful · 2026-05-13 23:39:12 UTC
Parallelism
87
/100
Blocked
14
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,421,128
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a050c18
#3
0x6a050c18
#4
updatePrices
· blocks 1
#6
updatePrices
#7
updatePrices
#8
0x6a050c18
#9
0x6a050c18
#10
0x000000b2
#11
updateDataFeedsValuesPartial
#12
setData
#13
0xed82b078
#14
fulfillOutcomes
#5
updatePrices
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
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x32ca4db5…4402
0x065c9d…c394
2 touches
0 conflicts
0x34c774bf…5d9e
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x769bead8…3caa
0x065c9d…c394
2 touches
0 conflicts
0x97fbaa91…997f
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:
0xab35264b…1cfa38
1 conflict on slot
0x0000000000…000002
Audit this contract →
← previous block
·
next block →
recent activity