pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,626,636
← previous block
next block →
recent activity
Analyzing
Block #90,626,636
12 transactions · 11 stateful · 2026-07-27 00:18:38 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,626,636
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
0x5a5d9a99
· blocks 1
#3
0x5a5d9a99
#4
0x0f6795d9
· blocks 1
#5
0x3f5c179b
#7
forward
#8
forward
#9
updateDataFeedsValuesPartial
#10
setData
#11
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
4
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc3d5171…8357
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x14c4e3ca…edd9
0x34b655…2a6f
4 touches
1 conflict
0x2132931c…59f7
0x34b655…2a6f
4 touches
1 conflict
0x224ff7ce…f233
0x34b655…2a6f
4 touches
1 conflict
0x2e19029d…72a7
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x38c6ff01…689f
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
0xfc3d51716d…008357
Audit this contract →
← previous block
·
next block →
recent activity