← previous blocknext block →recent activity

Analyzing

Block #72,978,121

15 transactions · 13 stateful · 2026-05-07 07:18:55 UTC

Parallelism

67/100

Blocked

46%

Avg conflicts / tx

0.6

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,978,121  ·  15 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x47c1a8e8…f74a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x5a3732cb…edb2

0x1b6862…e19c

4 touches
1 conflict

0x92d610a6…9a40

0x2a68ba…90c5

4 touches
1 conflict

0x35b85d8e…1edd

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

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

3 conflicts on slot 0x47c1a8e802…12f74a

← previous block·next block →recent activity