pev
.
One block, wave by wave
→
offline
by Silk Nodes →
pev
/
block
/
#72,284,539
← previous block
next block →
recent activity
Analyzing
Block #72,284,539
8 transactions · 8 stateful · 2026-05-04 02:17:19 UTC
Parallelism
75
/100
Blocked
13
%
Avg conflicts / tx
0.13
Longest chain
2
deep
Execution timeline
did this block parallelize well?
view
Execution
Conflict
Heatmap
block
#72,284,539
· 8 txs across 2 waves · depth 2
parallel ↔ serial
wave
w0
wave
w1
#0
syscallReward
#1
0x69f80226
#2
0x13828455
#3
0x9036287a
· blocks 1
#4
0x98717539
#5
setData
#6
0x0c7abd22
#7
0x3f5c179b
parallel · wave 0, no conflicts
delayed · forced to wait
conflict source · blocks others
Conflict graph
Blocked by
3
w0
7
w1
- write/write
- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x05c3b7fc…dfbd
0x065c9d…c394
2 touches
0 conflicts
0x12b5682d…3851
0x065c9d…c394
2 touches
0 conflicts
0x3df01dd5…1b02
0x065c9d…c394
2 touches
0 conflicts
0xd4841a9a…1278
0x065c9d…c394
2 touches
0 conflicts
0x74e71984…ae90
0x2a68ba…90c5
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:
0x065c9d28…a9c394
1 conflict on slot
0x0000000000…00003d
Audit this contract →
← previous block
·
next block →
recent activity