pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#76,224,879
← previous block
next block →
recent activity
Analyzing
Block #76,224,879
11 transactions · 9 stateful · 2026-05-22 08:28:08 UTC
Parallelism
82
/100
Blocked
22
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#76,224,879
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
updatePrices
#3
0x98717539
· blocks 1
#4
0xc2d867a5
· blocks 1
#7
0x0f6795d9
#8
forward
#9
0x6df9e92b
#10
setData
#5
0xc2d867a5
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w0
5
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0005
0x465a0b…3980
4 touches
1 conflict
0xc9c1648c…bea4
0x465a0b…3980
4 touches
1 conflict
0x17606ba6…1b6e
0x754704…b603
4 touches
1 conflict
0x2b131961…a433
0x754704…b603
4 touches
1 conflict
0xae160d77…159b
0x754704…b603
4 touches
1 conflict
0xb0f4dbcb…926a
0x754704…b603
4 touches
1 conflict
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
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:
0x465a0b35…b53980
1 conflict on slot
0x0000000000…000005
Audit this contract →
← previous block
·
next block →
recent activity