pev.One block, wave by wave
analytics
offline
by Silk Nodes →
← previous blocknext block →recent activity
Analyzing
Block #71,172,416
5 transactions · 4 stateful · 2026-04-28 22:41:06 UTC
Parallelism
60/100
Blocked
25%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,172,416 · 5 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x562aac99…ea83
0x065c9d…c394
4 touches
1 conflict
0x00027aae…b9c8
0x065c9d…c394
4 touches
1 conflict
0x0108aea0…1419
0x065c9d…c394
4 touches
1 conflict
0x76c7aed6…6860
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0xd0f8a6…badc
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7770ed8a…3098
0x065c9d…c394
2 touches
1 conflict
0xb0ae7ae3…3532
0x065c9d…c394
2 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
1 conflict on slot 0x562aac99e5…57ea83
Audit this contract →
← previous block·next block →recent activity