pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#74,238,337
← previous block
next block →
recent activity
Analyzing
Block #74,238,337
10 transactions · 8 stateful · 2026-05-13 03:23:18 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,238,337
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x67098489
#2
0x1ffa3c9b
#3
0x39435dac
· blocks 1
#4
updateDataFeedsValuesPartial
#6
execute
#7
forward
#8
setData
#9
0x39435dac
#5
0x98717539
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9b39579…408c
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x768cffcd…2648
0x34b655…2a6f
4 touches
1 conflict
0xa8ddf3d3…ece4
0x34b655…2a6f
4 touches
1 conflict
0x09453319…a296
0x065c9d…c394
2 touches
0 conflicts
0x46e6216f…5c45
0x065c9d…c394
2 touches
0 conflicts
0x7fabf04c…8a6a
0x065c9d…c394
2 touches
0 conflicts
0xa5a42c78…5ee1
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:
Perpl
1 conflict on slot
0xc9b3957972…08408c
Audit this contract →
← previous block
·
next block →
recent activity