pev
.
→
showcase
new
graph
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#90,545,912
← previous block
next block →
recent activity
Analyzing
Block #90,545,912
11 transactions · 11 stateful · 2026-07-26 17:32:32 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,545,912
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
updateDataFeedsValuesPartial
#2
executeBatch
#3
0x0f6795d9
· blocks 2
#5
0x3f5c179b
#7
0x6a664527
#8
transfer
#9
setData
#10
0x39435dac
#4
0x0f6795d9
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd9a771df…a27b
0x34b655…2a6f
4 touches
1 conflict
0xdb86d50f…b5fc
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5eb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x157536c0…33ef
0x34b655…2a6f
4 touches
1 conflict
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x3140cb7d…7bc0
0x34b655…2a6f
4 touches
1 conflict
0x3b666394…cae1
0x34b655…2a6f
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:
Perpl
1 conflict on slot
0xd9a771df76…baa27b
Audit this contract →
← previous block
·
next block →
recent activity