pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#97,710,688
← previous block
next block →
recent activity
Analyzing
Block #97,710,688
9 transactions · 8 stateful · 2026-08-20 19:47:21 UTC
Parallelism
78
/100
Blocked
25
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#97,710,688
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1ada0a83
#2
0xab083028
#3
execOrder
· blocks 1
#5
0x0c7abd22
#6
0x5acec890
· blocks 1
#8
0x59558d29
#4
execOrder
#7
0x5acec890
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4e22d6e8…5125
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x08897416…1c81
0x34b655…2a6f
2 touches
0 conflicts
0x2f4fd493…9935
0x34b655…2a6f
2 touches
0 conflicts
0x422f657b…279e
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
0x4e22d6e8a5…c25125
Audit this contract →
← previous block
·
next block →
recent activity