← previous blocknext block →recent activity
Analyzing
Block #73,963,282
14 transactions · 12 stateful · 2026-05-11 20:50:48 UTC
Parallelism
79/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,963,282 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w07w19w212w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2ed00f98…da9f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0xe95cd109…b34b
0xd32edf…ff58
5 touches
3 conflicts
0x20ac0567…c954
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
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: Perpl
3 conflicts on slot 0x2ed00f9866…11da9f
Audit this contract →
← previous block·next block →recent activity