pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,967,840
← previous block
next block →
recent activity
Analyzing
Block #101,967,840
9 transactions · 6 stateful · 2026-09-04 18:08:49 UTC
Parallelism
78
/100
Blocked
17
%
Avg conflicts / tx
0.11
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,967,840
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xdb834625
#2
execOrders
#3
0x000000b2
#4
execFwdPositionOpsV2
#5
setData
#6
0x000000b2
#7
execOrders
· blocks 1
#8
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
7
w0
8
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x03a10a92…98b7
0x34b655…2a6f
2 touches
0 conflicts
0x2e957c13…4777
0x34b655…2a6f
2 touches
0 conflicts
0x3027f5b0…7a3f
0x34b655…2a6f
2 touches
0 conflicts
0x38680dcf…3370
0x34b655…2a6f
2 touches
0 conflicts
0x3a02129f…9eaf
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
0xd98b3c102b…ca67b8
Audit this contract →
← previous block
·
next block →
recent activity