pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes →
pev
/
block
/
#74,627,217
← previous block
next block →
recent activity
Analyzing
Block #74,627,217
12 transactions · 8 stateful · 2026-05-14 22:38:50 UTC
Parallelism
83
/100
Blocked
25
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,627,217
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xaf850a…bffb
#2
swap
· blocks 1
#3
0xccf50a51
#4
0x5bf9264c
#5
0x5bf9264c
#6
updateDataFeedsValuesPartial
#8
closeBetting
#9
setData
#10
0x39435dac
· blocks 1
#7
0x62be7533
#11
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
7
w1
10
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xadac4a86…c2bc
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x74ad6e8c…fa0f
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x09beabbc…065d
0x188d58…ea8e
2 touches
0 conflicts
0x46cb45de…a566
0x188d58…ea8e
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:
0x34b6552d…112a6f
1 conflict on slot
0xadac4a860c…a3c2bc
Audit this contract →
← previous block
·
next block →
recent activity