pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,205,877
← previous block
next block →
recent activity
Analyzing
Block #102,205,877
16 transactions · 16 stateful · 2026-09-05 14:15:32 UTC
Parallelism
88
/100
Blocked
6
%
Avg conflicts / tx
0.06
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,205,877
· 16 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
swap
· blocks 1
#2
execOrders
#3
0x0c7abd22
#4
0xab083028
#5
0xab083028
#6
0x5acec890
#7
0x5acec890
#8
0x5acec890
#9
0x5acec890
#10
0x59558d29
#11
setData
#12
execFwdPositionOpsV2
#14
forward
#15
submitBatch
#13
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
13
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd868fb65…3b4a
0xe1c8b7…3022
4 touches
1 conflict
0x5b0621ee…3c2c
0x284f45…7777
4 touches
1 conflict
0x44ed742f…63f5
0x3bd359…433a
4 touches
1 conflict
0x4eb758b8…b13b
0x3bd359…433a
4 touches
1 conflict
0xdf409966…6b16
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x7aed55…0617
4 touches
1 conflict
0xa164d951…1534
0xe1c8b7…3022
4 touches
1 conflict
0x7462b8f2…6312
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:
0xe1c8b733…e33022
1 conflict on slot
0xd868fb65f1…2f3b4a
Audit this contract →
← previous block
·
next block →
recent activity