pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#102,206,076
← previous block
next block →
recent activity
Analyzing
Block #102,206,076
15 transactions · 14 stateful · 2026-09-05 14:16:32 UTC
Parallelism
80
/100
Blocked
14
%
Avg conflicts / tx
0.2
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#102,206,076
· 15 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
swap
· blocks 2
#2
0xab083028
#3
0xab083028
#4
0xab083028
#6
0x5acec890
#7
0x5acec890
#8
0x59558d29
#10
forward
#11
transfer
#12
0x6a9c2442
#13
setData
#14
execOrders
#5
permit2TransferAndMulticall
· blocks 1
#9
handleOps
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
5
w1
9
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0004
0x7aed55…0617
6 touches
3 conflicts
0xdf409966…6b16
0x3bd359…433a
6 touches
3 conflicts
0xa164d951…1534
0xe1c8b7…3022
6 touches
3 conflicts
0x4eb758b8…b13b
0x3bd359…433a
6 touches
3 conflicts
0x5b0621ee…3c2c
0x284f45…7777
6 touches
3 conflicts
0x44ed742f…63f5
0x3bd359…433a
6 touches
3 conflicts
0xd868fb65…3b4a
0xe1c8b7…3022
5 touches
3 conflicts
0x00000000…0004
0x5afd3e…7620
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:
0x7aed5536…6a0617
3 conflicts on slot
0x0000000000…000004
Audit this contract →
← previous block
·
next block →
recent activity