pev
.
→
scale
new
showcase
graph
analytics
feedback
offline
by Silk Nodes
pev
/
block
/
#90,448,233
← previous block
next block →
recent activity
Analyzing
Block #90,448,233
8 transactions · 8 stateful · 2026-07-26 09:21:09 UTC
Parallelism
63
/100
Blocked
25
%
Avg conflicts / tx
0.25
Longest chain
3
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#90,448,233
· 8 txs across 3 waves · depth 3
parallel ↔ serial
wave
w0
wave
w1
wave
w2
#0
syscallReward
#1
0x5a5d9a99
· blocks 1
#2
0x5a5d9a99
#5
forward
#6
0x39435dac
#7
setData
#3
0x0f6795d9
· blocks 1
#4
0x0f6795d9
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
3
w1
4
w2
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec501e17…45fd
0x34b655…2a6f
4 touches
1 conflict
0x300ea4a0…ee47
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x262d4253…b091
0x34b655…2a6f
2 touches
0 conflicts
0x3c78ca04…432c
0x34b655…2a6f
2 touches
0 conflicts
0x3ebb403d…3a8f
0x34b655…2a6f
2 touches
0 conflicts
0x4699a63a…eddc
0x34b655…2a6f
2 touches
0 conflicts
0x5251466a…41d6
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
0xec501e1764…5245fd
Audit this contract →
← previous block
·
next block →
recent activity