pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #72,283,562
13 transactions · 12 stateful · 2026-05-04 02:10:45 UTC
Parallelism
69/100
Blocked
58%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,283,562 · 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
1w02w03w14w16w27w08w19w311w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe54a1f6f…18f2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x74e71984…ae90
0x2a68ba…90c5
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: 0x34b6552d…112a6f
3 conflicts on slot 0xe54a1f6fdd…7918f2
Audit this contract →
← previous block·next block →recent activity