← previous blocknext block →recent activity

Analyzing

Block #73,600,323

29 transactions · 17 stateful · 2026-05-10 04:18:08 UTC

Parallelism

72/100

Blocked

53%

Avg conflicts / tx

1.03

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,600,323  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x60aca8aa…1bb2

0xd32edf…ff58

15 touches
28 conflicts

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xda1a7071…22ff

0x065c9d…c394

4 touches
1 conflict

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb82

0x1b6862…e19c

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x6060de18…3272

0x065c9d…c394

2 touches
0 conflicts

0x16005c59…cd79

0x754704…b603

2 touches
0 conflicts

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

28 conflicts on slot 0x60aca8aa5f…b31bb2

← previous block·next block →recent activity