pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#100,128,025
← previous block
next block →
recent activity
Analyzing
Block #100,128,025
9 transactions · 9 stateful · 2026-08-29 07:44:54 UTC
Parallelism
78
/100
Blocked
22
%
Avg conflicts / tx
0.22
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#100,128,025
· 9 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x59558d29
· blocks 1
#3
setData
#4
0x94defb17
· blocks 1
#6
execFwdPositionOpsV2
#7
0x6a928e6e
#8
execOrders
#2
0x59558d29
#5
0x94defb17
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
4
w0
5
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef3cca9f…fa04
0x8964d7…10f8
4 touches
1 conflict
0xeae4fbd4…89b8
0x8964d7…10f8
4 touches
1 conflict
0xeae4fbd4…89b9
0x8964d7…10f8
4 touches
1 conflict
0xeae4fbd4…89bb
0x8964d7…10f8
4 touches
1 conflict
0xef3cca9f…f9fe
0x8964d7…10f8
4 touches
1 conflict
0xef3cca9f…f9ff
0x8964d7…10f8
4 touches
1 conflict
0xef3cca9f…fa02
0x8964d7…10f8
4 touches
1 conflict
0xef3cca9f…fa03
0x8964d7…10f8
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:
0x8964d7c9…5b10f8
1 conflict on slot
0xef3cca9fd0…fcfa04
Audit this contract →
← previous block
·
next block →
recent activity