pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#103,215,663
← previous block
next block →
recent activity
Analyzing
Block #103,215,663
12 transactions · 9 stateful · 2026-09-09 03:17:01 UTC
Parallelism
75
/100
Blocked
22
%
Avg conflicts / tx
0.17
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#103,215,663
· 12 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
execOrders
· blocks 1
#2
0xab083028
#3
0x5acec890
#4
0x5acec890
#5
0x59558d29
#6
0x41a8f47c
#7
setData
#8
0xe72fc2…c277
#11
0xd37793…7dd8
#9
execOrders
· blocks 1
#10
execOrders
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
9
w1
10
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2905ed39…1865
0x34b655…2a6f
4 touches
1 conflict
0x31861539…8ae9
0x34b655…2a6f
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x03f08d80…0661
0x34b655…2a6f
2 touches
0 conflicts
0x0d5f7a7f…9314
0x34b655…2a6f
2 touches
0 conflicts
0x0f13b598…f75b
0x34b655…2a6f
2 touches
0 conflicts
0x12960d2c…99f9
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
0x2905ed393b…f81865
Audit this contract →
← previous block
·
next block →
recent activity