← previous blocknext block →recent activity

Analyzing

Block #73,949,046

16 transactions · 14 stateful · 2026-05-11 19:16:11 UTC

Parallelism

56/100

Blocked

57%

Avg conflicts / tx

1.5

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,949,046  ·  16 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x44ad89ba…cf83

0x7131ec…7777

14 touches
21 conflicts

0xa472d565…9fe4

0x3bd359…433a

14 touches
21 conflicts

0xaa3e5ab2…fd8a

0x3bd359…433a

14 touches
21 conflicts

0x00000000…0001

0xc82b5c…bb3a

14 touches
21 conflicts

0xd46cd782…e7f2

0x7131ec…7777

14 touches
21 conflicts

0x00000000…0000

0xc82b5c…bb3a

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xc08384da…ecb7

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: 0x7131eca3…f77777

21 conflicts on slot 0x44ad89ba62…49cf83

← previous block·next block →recent activity