← previous blocknext block →recent activity
Analyzing
Block #73,036,612
30 transactions · 22 stateful · 2026-05-07 13:48:12 UTC
Parallelism
87/100
Blocked
41%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,036,612 · 30 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
1w02w13w06w07w111w212w316w017w123w124w225w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd574ca…7ab1
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x8a35acfb…d1ab
0x8d66a4…3095
4 touches
1 conflict
0xe89e1a22…ce49
0x8d66a4…3095
4 touches
1 conflict
0xce7bfe5e…5e58
0x065c9d…c394
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: 0xd574cae5…037ab1
6 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity