pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#101,989,475
← previous block
next block →
recent activity
Analyzing
Block #101,989,475
12 transactions · 12 stateful · 2026-09-04 19:58:33 UTC
Parallelism
83
/100
Blocked
17
%
Avg conflicts / tx
0.17
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#101,989,475
· 12 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
execOrders
· blocks 1
#2
updatePrices
#3
0xab083028
#4
0xab083028
#5
0x5acec890
#6
0x3e2e8792
#7
execPerpOps
· blocks 1
#9
0xf5d05576
#10
0x6a9b2361
#8
execPerpOps
#11
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
7
w0
8
w1
11
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…1266
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x01315072…0e2d
0x34b655…2a6f
2 touches
0 conflicts
0x08c5d8d8…c7c1
0x34b655…2a6f
2 touches
0 conflicts
0x0bb33e3f…7072
0x34b655…2a6f
2 touches
0 conflicts
0x0c2ad474…a331
0x34b655…2a6f
2 touches
0 conflicts
0x1577dd4a…550d
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
0x51fc8795c8…571266
Audit this contract →
← previous block
·
next block →
recent activity