pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#76,481,453
← previous block
next block →
recent activity
Analyzing
Block #76,481,453
13 transactions · 11 stateful · 2026-05-23 12:56:26 UTC
Parallelism
77
/100
Blocked
36
%
Avg conflicts / tx
0.31
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,481,453
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#3
execute_route
· blocks 1
#6
exactOutputSingle
#7
execute
#8
setData
#9
0x98717539
#10
updateDataFeedsValuesPartial
#11
0x39435dac
· blocks 1
#2
0x0c7abd22
#4
execute_route
· blocks 1
#12
0x39435dac
#5
exactOutputSingle
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
3
w0
4
w1
5
w2
11
w0
12
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0xd5b70d…615b
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0d4d87fc…4080
0x065c9d…c394
4 touches
1 conflict
0x18cf3003…51d1
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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:
0xd5b70d70…f4615b
1 conflict on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity