pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,835,785
← previous block
next block →
recent activity
Analyzing
Block #90,835,785
9 transactions · 8 stateful · 2026-07-27 17:50:54 UTC
Parallelism
78
/100
Blocked
13
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,835,785
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
execute
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
#5
updateDataFeedsValuesPartial
#7
setData
#8
0x39435dac
#6
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7729d2c9…8c22
0x34b655…2a6f
4 touches
1 conflict
0x7729d2c9…8c23
0x34b655…2a6f
4 touches
1 conflict
0x1ee6a8c8…026f
0x34b655…2a6f
4 touches
1 conflict
0x606bc50d…4c10
0x34b655…2a6f
4 touches
1 conflict
0xb9266685…8b1d
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2ae990e1…293b
0x34b655…2a6f
2 touches
0 conflicts
0x2eedcc6d…f35c
0x34b655…2a6f
2 touches
0 conflicts
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
0x7729d2c9a5…c58c22
Audit this contract →
← previous block
·
next block →
recent activity