pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,112,714
← previous block
next block →
recent activity
Analyzing
Block #76,112,714
12 transactions · 11 stateful · 2026-05-21 20:01:03 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,112,714
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xc5a04723
#2
relay
#3
forward
#4
execute
#5
updateDataFeedsValuesPartial
#6
updateDataFeedsValuesPartial
#7
0xe9316489
#8
setData
#9
execOrders
· blocks 1
#11
execOrders
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
9
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0xe75ce681…ba5f
0x188d58…ea8e
2 touches
0 conflicts
0xe75ce681…ba61
0x188d58…ea8e
2 touches
0 conflicts
0x754493a0…e69b
0x3bd359…433a
2 touches
0 conflicts
0x588e01f1…6a3a
0x3e4f2b…ba84
2 touches
0 conflicts
0x2bd6057a…370c
0x6f92c7…6a92
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity