← previous blocknext block →recent activity

Analyzing

Block #73,499,685

15 transactions · 12 stateful · 2026-05-09 17:09:17 UTC

Parallelism

40/100

Blocked

67%

Avg conflicts / tx

2.4

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,499,685  ·  15 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x00000000…0001

0x3704e4…e36f

18 touches
36 conflicts

0xa472d565…9fe4

0x3bd359…433a

18 touches
36 conflicts

0xea8e8e68…ba34

0x3bd359…433a

18 touches
36 conflicts

0x44ad89ba…cf83

0xb68427…7777

18 touches
36 conflicts

0x8b144217…a58e

0xb68427…7777

18 touches
36 conflicts

0x00000000…0000

0x3704e4…e36f

18 touches
36 conflicts

0x689cd5fd…5556

0x34b655…2a6f

2 touches
0 conflicts

0x89999c15…fdac

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: 0x3704e421…3ae36f

36 conflicts on slot 0x0000000000…000001

← previous block·next block →recent activity