pev
.
One block, wave by wave
→
analytics
docs
feedback
offline
by Silk Nodes
pev
/
block
/
#72,426,128
← previous block
next block →
recent activity
Analyzing
Block #72,426,128
10 transactions · 9 stateful · 2026-05-04 18:01:21 UTC
Parallelism
80
/100
Blocked
11
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,426,128
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x1a945f9c
· blocks 1
#3
0x3f5c179b
#4
0x6df9e92b
#5
setData
#6
0x39435dac
#7
0x39435dac
#8
0x39435dac
#9
0x39435dac
#2
0x366fe5db
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
2
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00bac013…a28c
0xfd44b3…00d1
4 touches
1 conflict
0xb6b74ae0…8d5e
0xea1b8e…c5ec
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…006f
0x1efe02…37d6
2 touches
0 conflicts
0x2a2bacfe…6a55
0x1efe02…37d6
2 touches
0 conflicts
0x5f53a383…ac9b
0x1efe02…37d6
2 touches
0 conflicts
0x99a4e340…debc
0x1efe02…37d6
2 touches
0 conflicts
0x00000000…0099
0xaa3145…feec
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:
0xfd44b351…7f00d1
1 conflict on slot
0x00bac0131a…bba28c
Audit this contract →
← previous block
·
next block →
recent activity