pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,860,798
14 transactions · 12 stateful · 2026-05-06 18:18:03 UTC
Parallelism
57/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,860,798 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w38w49w513w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x17f99a3a…6b55
0x065c9d…c394
4 touches
1 conflict
0x30285dbb…3745
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
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: 0x065c9d28…a9c394
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity