pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,801,441
← previous block
next block →
recent activity
Analyzing
Block #101,801,441
14 transactions · 13 stateful · 2026-09-04 04:08:34 UTC
Parallelism
86
/100
Blocked
15
%
Avg conflicts / tx
0.14
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,801,441
· 14 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x0c7abd22
· blocks 1
#2
matchOrders
#4
0x5acec890
#5
0x5acec890
#6
0x59558d29
· blocks 1
#8
execPerpOps
#9
execPerpOps
#10
executeBatch
#11
setData
#12
forward
#13
0x6a9a44ba
#3
execOrders
#7
0x59558d29
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
6
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7ea9d5d4…8219
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xb65aaedf…e6d9
0x34b655…2a6f
4 touches
1 conflict
0xca70fa2c…6a7e
0x34b655…2a6f
4 touches
1 conflict
0xd688757b…292b
0x34b655…2a6f
4 touches
1 conflict
0xff5736d9…89d3
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
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
0x7ea9d5d41d…7e8219
Audit this contract →
← previous block
·
next block →
recent activity