pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#106,543,817
← previous block
next block →
recent activity
Analyzing
Block #106,543,817
9 transactions · 8 stateful · 2026-09-20 19:14:02 UTC
Parallelism
67
/100
Blocked
25
%
Avg conflicts / tx
0.33
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#106,543,817
· 9 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0xab083028
#2
0x928e4afa
#3
0xb2d4797b
· blocks 2
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
execOrders
#4
0xb2d4797b
· blocks 1
#5
0xb2d4797b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
4
w1
5
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
6 touches
3 conflicts
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x045532dd…4b7d
0x34b655…2a6f
2 touches
0 conflicts
0x0a0d0bdf…5370
0x34b655…2a6f
2 touches
0 conflicts
0x1d13f4b8…0846
0x34b655…2a6f
2 touches
0 conflicts
0x35cf4d78…c461
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:
0x59df8637…6d2780
3 conflicts on slot
0x0000000000…000031
Audit this contract →
← previous block
·
next block →
recent activity