pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,087,888
← previous block
next block →
recent activity
Analyzing
Block #101,087,888
11 transactions · 11 stateful · 2026-09-01 16:18:46 UTC
Parallelism
82
/100
Blocked
18
%
Avg conflicts / tx
0.18
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,087,888
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
0x5acec890
#4
aggregate3
#5
execFwdPositionOpsV2
· blocks 1
#6
updateTemporalNumericValuesV1
#8
transfer
#9
0x6a96fb5e
#10
setData
#3
0x0c7abd22
#7
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
5
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcec3ed3…26a9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x7cdeb715…bfce
0x34b655…2a6f
4 touches
1 conflict
0x7dbeccfc…8faf
0x34b655…2a6f
4 touches
1 conflict
0x856cc545…fd78
0x34b655…2a6f
4 touches
1 conflict
0xca713a35…abfd
0x34b655…2a6f
4 touches
1 conflict
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
0xfcec3ed372…de26a9
Audit this contract →
← previous block
·
next block →
recent activity