← previous blocknext block →recent activity

Analyzing

Block #73,049,641

14 transactions · 13 stateful · 2026-05-07 15:15:00 UTC

Parallelism

57/100

Blocked

38%

Avg conflicts / tx

1.07

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,049,641  ·  14 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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…0002

0xab3526…fa38

12 touches
15 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xf16bd40a…b294

0x000000…8ba3

2 touches
0 conflicts

0x00000000…0036

0x386489…7508

2 touches
0 conflicts

0x1a920eda…bfae

0x386489…7508

2 touches
0 conflicts

0x15bae5fc…9f7e

0x57ea24…2cec

2 touches
0 conflicts

0x4aecce30…a99b

0x57ea24…2cec

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: 0xab35264b…1cfa38

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity