← previous blocknext block →recent activity

Analyzing

Block #72,366,373

12 transactions · 12 stateful · 2026-05-04 11:23:05 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #72,366,373  ·  12 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

0x50059a18…9b7b

0x34b655…2a6f

6 touches
3 conflicts

0xf763cad4…23f1

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0x1c913164…5c2e

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x5a3732cb…edae

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

3 conflicts on slot 0x50059a187b…bc9b7b

← previous block·next block →recent activity