← previous blocknext block →recent activity

Analyzing

Block #73,603,608

18 transactions · 16 stateful · 2026-05-10 04:39:55 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,603,608  ·  18 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x8240d70c…7c3b

0x34b655…2a6f

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0xb2b232c1…8871

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

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: 0x34b6552d…112a6f

6 conflicts on slot 0x8240d70c8a…f27c3b

← previous block·next block →recent activity