pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,026,188
← previous block
next block →
recent activity
Analyzing
Block #100,026,188
11 transactions · 8 stateful · 2026-08-28 23:12:13 UTC
Parallelism
82
/100
Blocked
13
%
Avg conflicts / tx
0.09
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,026,188
· 11 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xdae900…6d9c
#2
0x6ad2e98b
#3
execOrders
#4
execOrders
#5
0x59558d29
#6
0x59558d29
#7
execFwdPositionOpsV2
#8
execFwdPositionOpsV2
· blocks 1
#9
setData
#10
execFwdPositionOpsV2
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
8
w0
10
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0x15b5f87e…b707
0x34b655…2a6f
4 touches
1 conflict
0x33a52005…0530
0x34b655…2a6f
4 touches
1 conflict
0x3f9a1b4b…664e
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e25
0x34b655…2a6f
4 touches
1 conflict
0xa4f6a0ed…6e26
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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
0xe945730196…1083cd
Audit this contract →
← previous block
·
next block →
recent activity