← previous blocknext block →recent activity

Analyzing

Block #73,805,108

18 transactions · 12 stateful · 2026-05-11 03:17:36 UTC

Parallelism

67/100

Blocked

42%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,805,108  ·  18 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

0x43b5fc5d…58ee

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb87

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x088516d8…12c0

0xa6afd3…d132

3 touches
1 conflict

0x09000000…0001

0x000000…1000

2 touches
0 conflicts

0xdd70bea3…1ffe

0x3bd359…433a

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: 0xd32edf66…9fff58

15 conflicts on slot 0x43b5fc5db6…aa58ee

← previous block·next block →recent activity