pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,399,335
13 transactions · 13 stateful · 2026-05-04 15:02:47 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,399,335 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0001
0x37b81d…17d7
8 touches
6 conflicts
0x3b23d356…dcda
0x3bd359…433a
8 touches
6 conflicts
0x551f6273…7c20
0x42a4aa…7777
8 touches
6 conflicts
0x00000000…0003
0x37b81d…17d7
8 touches
6 conflicts
0x00000000…0000
0x37b81d…17d7
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
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: 0x37b81dc0…2e17d7
6 conflicts on slot 0x0000000000…000001
Audit this contract →
← previous block·next block →recent activity