pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#98,060,802
← previous block
next block →
recent activity
Analyzing
Block #98,060,802
12 transactions · 11 stateful · 2026-08-22 01:24:09 UTC
Parallelism
83
/100
Blocked
9
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#98,060,802
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x7b84f330
· blocks 1
#2
0x41a8f47c
#3
0x41a8f47c
#4
postStateList
#5
execOrders
#6
0x32d01e04
#7
0x59558d29
#8
0x5acec890
#9
0xed82b078
#10
setData
#11
0x7b84f330
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0007
0x340143…768f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x27d1cd54…fbd3
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
2 touches
0 conflicts
0x81955a0a…29ee
0x340143…768f
2 touches
0 conflicts
0x4d1e3e31…edf8
0x3bd359…433a
2 touches
0 conflicts
0x997ccc40…4dfd
0x3bd359…433a
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:
0x34014398…d1768f
1 conflict on slot
0x0000000000…000007
Audit this contract →
← previous block
·
next block →
recent activity