pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,564,284
← previous block
next block →
recent activity
Analyzing
Block #98,564,284
10 transactions · 9 stateful · 2026-08-23 19:50:34 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,564,284
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xdb834625
#2
0x6ad2e98b
#3
0xab083028
#4
0x59558d29
#5
0x3f5c179b
· blocks 1
#7
setData
#8
0x02dfdd…4bb0
#9
execOrders
#6
batchUpdate
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
5
w0
6
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99b29f97…d502
0x851145…3f07
4 touches
1 conflict
0xee7c63cc…88de
0x851145…3f07
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x5c5dffb4…0ab4
0x851145…3f07
4 touches
1 conflict
0x00000000…0005
0x19f079…1d56
2 touches
0 conflicts
0x1afbc11d…e909
0x19f079…1d56
2 touches
0 conflicts
0x002fed35…79fa
0x2a68ba…90c5
2 touches
0 conflicts
0x1c912a68…3b21
0x2a68ba…90c5
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:
0x851145ea…9f3f07
1 conflict on slot
0x99b29f975c…bed502
Audit this contract →
← previous block
·
next block →
recent activity