pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,067,913
← previous block
next block →
recent activity
Analyzing
Block #101,067,913
12 transactions · 10 stateful · 2026-09-01 14:38:09 UTC
Parallelism
83
/100
Blocked
10
%
Avg conflicts / tx
0.08
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,067,913
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x5acec890
· blocks 1
#2
0xab083028
#3
0x0c7abd22
#4
0x5acec890
#5
execFwdPositionOpsV2
#6
bet
#7
transfer
#8
setData
#9
execOrders
#10
execOrders
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42d6dd00…1c9d
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0b7b942e…f3f4
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x2251e657…1ab5
0x34b655…2a6f
2 touches
0 conflicts
0x24dc9eeb…1126
0x34b655…2a6f
2 touches
0 conflicts
0x29a58269…011a
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
0x42d6dd00e3…041c9d
Audit this contract →
← previous block
·
next block →
recent activity