pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,707,088
← previous block
next block →
recent activity
Analyzing
Block #90,707,088
11 transactions · 9 stateful · 2026-07-27 07:03:21 UTC
Parallelism
82
/100
Blocked
11
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,707,088
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
update
#2
executeMessage
#3
0x5a5d9a99
· blocks 1
#5
0x0f6795d9
#6
updateDataFeedsValuesPartial
#7
0xed82b078
#8
0x0f6795d9
#9
setData
#10
0x39435dac
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5ab7b8a…c97b
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…0002
0x09aea4…ec64
2 touches
0 conflicts
0x0c376bba…95b1
0x34b655…2a6f
2 touches
0 conflicts
0x35bce9bd…620e
0x34b655…2a6f
2 touches
0 conflicts
0x3d4c0233…20a5
0x34b655…2a6f
2 touches
0 conflicts
0x4a6982a4…158c
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
0xa5ab7b8a6d…b0c97b
Audit this contract →
← previous block
·
next block →
recent activity