← previous blocknext block →recent activity

Analyzing

Block #73,921,596

22 transactions · 14 stateful · 2026-05-11 16:13:35 UTC

Parallelism

73/100

Blocked

64%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,921,596  ·  22 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x43e495f2…4d0e

0xd32edf…ff58

11 touches
15 conflicts

0x3565f8b6…83fb

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

6 touches
3 conflicts

0xee230b20…5a0f

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

4 touches
1 conflict

0x17a7f697…dcb2

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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: 0xd32edf66…9fff58

15 conflicts on slot 0x43e495f29a…c04d0e

← previous block·next block →recent activity