← previous blocknext block →recent activity

Analyzing

Block #73,476,081

18 transactions · 15 stateful · 2026-05-09 14:32:11 UTC

Parallelism

67/100

Blocked

40%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,476,081  ·  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

0x00000000…0000

0x116e7d…d8f1

12 touches
15 conflicts

0x00000000…0002

0x116e7d…d8f1

12 touches
15 conflicts

0x00000000…0003

0x116e7d…d8f1

12 touches
15 conflicts

0x692a4122…76b8

0x350035…7777

12 touches
15 conflicts

0xb7143610…adc4

0x3bd359…433a

12 touches
15 conflicts

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x20ac0567…c954

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

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: 0x116e7d07…d7d8f1

15 conflicts on slot 0x0000000000…000000

← previous block·next block →recent activity