← previous blocknext block →recent activity

Analyzing

Block #73,446,748

16 transactions · 14 stateful · 2026-05-09 11:17:00 UTC

Parallelism

50/100

Blocked

50%

Avg conflicts / tx

1.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,446,748  ·  16 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

0xea8e8e68…ba34

0x3bd359…433a

16 touches
28 conflicts

0x00000000…0000

0x3704e4…e36f

16 touches
28 conflicts

0x00000000…0001

0x3704e4…e36f

16 touches
28 conflicts

0x44ad89ba…cf83

0xb68427…7777

16 touches
28 conflicts

0x8b144217…a58e

0xb68427…7777

16 touches
28 conflicts

0xa472d565…9fe4

0x3bd359…433a

16 touches
28 conflicts

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

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: 0x3bd359c1…15433a

28 conflicts on slot 0xea8e8e68fd…eeba34

← previous block·next block →recent activity