pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,205,552
← previous block
next block →
recent activity
Analyzing
Block #102,205,552
13 transactions · 13 stateful · 2026-09-05 14:13:53 UTC
Parallelism
77
/100
Blocked
15
%
Avg conflicts / tx
0.23
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,205,552
· 13 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x0c7abd22
#2
0xa96df62f
#3
0xab083028
#4
approve
· blocks 1
#6
approve
#7
approve
· blocks 1
#9
execOrders
#10
updateDataFeedsValuesPartial
#11
0x59558d29
#12
execOrders
#5
swap
· blocks 1
#8
swap
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
4
w0
5
w1
7
w0
8
w2
- 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
0x00000000…002f
0x1b6862…e19c
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