pev
.
One block, wave by wave
→
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,307,964
← previous block
next block →
recent activity
Analyzing
Block #74,307,964
13 transactions · 8 stateful · 2026-05-13 11:06:22 UTC
Parallelism
85
/100
Blocked
25
%
Avg conflicts / tx
0.15
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,307,964
· 13 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
#2
0x6a045ba6
#3
0x6a045ba6
#4
0x98717539
· blocks 1
#6
updateDataFeedsValuesPartial
#7
withdraw
#8
0xd10227eb
· blocks 1
#10
0x6a045ba6
#11
setData
#12
0x39435dac
#5
0x98717539
#9
0xd10227eb
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3dbd9177…e936
0xea1b8e…c5ec
4 touches
1 conflict
0x6eff5416…605d
0xea1b8e…c5ec
4 touches
1 conflict
0xc6417de0…2191
0xc8689a…ee79
4 touches
1 conflict
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0015
0x1b6862…e19c
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:
LeverUp: LeverUp
1 conflict on slot
0x3dbd917768…a6e936
Audit this contract →
← previous block
·
next block →
recent activity