pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,125,980
← previous block
next block →
recent activity
Analyzing
Block #90,125,980
15 transactions · 13 stateful · 2026-07-25 06:04:06 UTC
Parallelism
87
/100
Blocked
8
%
Avg conflicts / tx
0.07
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,125,980
· 15 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x6ad2e98b
#2
execFwdPositionOps
#3
execFwdPositionOps
#4
executeBatch
#5
0x6a64524e
#6
setData
#7
withdraw
#8
execOrders
· blocks 1
#10
execOrders
#11
execOrders
#12
execOrders
#13
execOrders
#14
execOrders
#9
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
9
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x67bfbc55…7b2f
0x34b655…2a6f
4 touches
1 conflict
0x733a5000…6e67
0x34b655…2a6f
4 touches
1 conflict
0xa124184b…1dcb
0x34b655…2a6f
4 touches
1 conflict
0xaf151f7f…3fe4
0x34b655…2a6f
4 touches
1 conflict
0xc1917885…8fd2
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe209185c…b657
0x34b655…2a6f
4 touches
1 conflict
0xe999cbf5…d18a
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
0x67bfbc5533…247b2f
Audit this contract →
← previous block
·
next block →
recent activity