pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,886,200
← previous block
next block →
recent activity
Analyzing
Block #90,886,200
11 transactions · 11 stateful · 2026-07-27 22:04:33 UTC
Parallelism
82
/100
Blocked
9
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,886,200
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5a5d9a99
#2
updateDataFeedsValuesPartial
#3
0x532c46db
· blocks 1
#5
0x3f5c179b
#6
0x0f6795d9
#7
0x0f6795d9
#8
0x6a67d668
#9
setData
#10
0xc7e3ec2c
#4
0x532c46db
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
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3bb7be7f…8347
0x851145…3f07
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0xf13704e6…258a
0x01bff4…1071
2 touches
0 conflicts
0xa243ce39…3ff4
0x34b655…2a6f
2 touches
0 conflicts
0xa9660e2b…64df
0x34b655…2a6f
2 touches
0 conflicts
0xb3e53c5e…b99c
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:
Kuru Exchange: MarginAccount
1 conflict on slot
0x07b86c515d…73cdae
Audit this contract →
← previous block
·
next block →
recent activity