pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#74,442,524
← previous block
next block →
recent activity
Analyzing
Block #74,442,524
12 transactions · 8 stateful · 2026-05-14 02:01:46 UTC
Parallelism
83
/100
Blocked
13
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#74,442,524
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
execOrders
#3
get_block_hash_257335279069929
#4
0xd10227eb
#5
0xed82b078
#6
setData
#7
execOrders
· blocks 1
#8
execOrders
#9
execOrders
#11
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef17b8cd…9511
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0x041ee703…b4c1
0x34b655…2a6f
2 touches
0 conflicts
0x06db03a6…4692
0x34b655…2a6f
2 touches
0 conflicts
0x0d3d3160…bb17
0x34b655…2a6f
2 touches
0 conflicts
0x85a88798…f85e
0x34b655…2a6f
2 touches
0 conflicts
0x8cea5724…5c29
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
0xef17b8cd5c…709511
Audit this contract →
← previous block
·
next block →
recent activity