pev
.
One block, wave by wave
→
analytics
offline
by Silk Nodes →
pev
/
block
/
#72,224,612
← previous block
next block →
recent activity
Analyzing
Block #72,224,612
10 transactions · 8 stateful · 2026-05-03 19:34:31 UTC
Parallelism
80
/100
Blocked
13
%
Avg conflicts / tx
0.1
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,224,612
· 10 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0xe7be4706
· blocks 1
#2
0x98717539
#3
updateDataFeedsValuesPartial
#5
0xe7be4706
#6
0x3f5c179b
#7
0x69f7a3bf
#8
setData
#9
0x39435dac
#4
0xe7be4706
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
1
w0
4
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe6455d1f…1029
0x754704…b603
4 touches
1 conflict
0x0d0b2509…074d
0x3bd359…433a
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1179284b…db76
0x34b655…2a6f
2 touches
0 conflicts
0x1c913164…5c2e
0x34b655…2a6f
2 touches
0 conflicts
0x8db1e0f2…2fcf
0x34b655…2a6f
2 touches
0 conflicts
0xaa3492db…3703
0x34b655…2a6f
2 touches
0 conflicts
0xc3aacf13…6b3d
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:
0x754704bc…afb603
1 conflict on slot
0xe6455d1fbe…eb1029
Audit this contract →
← previous block
·
next block →
recent activity