pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,024,974
← previous block
next block →
recent activity
Analyzing
Block #74,024,974
11 transactions · 9 stateful · 2026-05-12 03:44:01 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,024,974
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0x98717539
· blocks 1
#3
forward
#4
updateDataFeedsValuesPartial
#5
updateDataFeedsValuesPartial
#6
setData
#7
0x39435dac
#9
0x39435dac
#10
0x39435dac
#8
0x39435dac
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7b97d40a…09ed
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x4f483049…3cc7
0x34b655…2a6f
2 touches
0 conflicts
0x5de96bd3…c60c
0x34b655…2a6f
2 touches
0 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0x9be2b99a…a959
0x34b655…2a6f
2 touches
0 conflicts
0xbc3d6b37…2215
0x34b655…2a6f
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
0x7b97d40a0c…6409ed
Audit this contract →
← previous block
·
next block →
recent activity