pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,802,543
← previous block
next block →
recent activity
Analyzing
Block #90,802,543
9 transactions · 7 stateful · 2026-07-27 15:03:35 UTC
Parallelism
78
/100
Blocked
29
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,802,543
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x4c9802…5e0c
#2
0xab083028
· blocks 1
#3
0x0f6795d9
· blocks 1
#6
updateDataFeedsValuesPartial
#7
0x6a6773bf
#8
setData
#4
0x0f6795d9
#5
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
2
w0
3
w0
4
w1
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf5947e44…c73f
0x40c49f…2af0
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x40a6de3a…0973
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x810a3aa2…0227
0x34b655…2a6f
4 touches
1 conflict
0x895f9add…5bac
0x34b655…2a6f
4 touches
1 conflict
0x9ba6ae4a…90cb
0x34b655…2a6f
4 touches
1 conflict
0xbb8dc535…4fe7
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:
0x40c49f17…d22af0
1 conflict on slot
0xf5947e446e…01c73f
Audit this contract →
← previous block
·
next block →
recent activity