pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#99,819,387
← previous block
next block →
recent activity
Analyzing
Block #99,819,387
8 transactions · 7 stateful · 2026-08-28 05:49:32 UTC
Parallelism
75
/100
Blocked
14
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#99,819,387
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execute
#2
0xab083028
#3
0x5acec890
#4
0x5acec890
#5
0x3f5c179b
#6
execFwdPositionOpsV2
· blocks 1
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0e974c4…b84d
0x34b655…2a6f
4 touches
1 conflict
0xd8746a08…f894
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0xa1bfcd69…07cf
0x34b655…2a6f
4 touches
1 conflict
0x5b6af007…0f35
0x34b655…2a6f
4 touches
1 conflict
0x6434c774…f635
0x34b655…2a6f
2 touches
0 conflicts
0x75f928fc…0465
0x34b655…2a6f
2 touches
0 conflicts
0xac206e47…ef7d
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
0xb0e974c47d…53b84d
Audit this contract →
← previous block
·
next block →
recent activity