← previous blocknext block →recent activity

Analyzing

Block #73,273,901

18 transactions · 16 stateful · 2026-05-08 16:06:56 UTC

Parallelism

83/100

Blocked

31%

Avg conflicts / tx

0.39

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,273,901  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

6 touches
3 conflicts

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0x01e85262…3e92

0x000000…012a

2 touches
0 conflicts

0xd9928549…aa6a

0x000000…012a

2 touches
0 conflicts

0x28bce6ed…1d79

0x0555e3…2b9c

2 touches
0 conflicts

0x23a320fb…cbd7

0x34b655…2a6f

2 touches
0 conflicts

0x31ea0355…e23f

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity