← previous blocknext block →recent activity

Analyzing

Block #73,749,108

19 transactions · 17 stateful · 2026-05-10 20:59:55 UTC

Parallelism

47/100

Blocked

53%

Avg conflicts / tx

2.37

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,749,108  ·  19 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

2 touches
0 conflicts

0x157b6348…8604

0x34b655…2a6f

2 touches
0 conflicts

0x20ac0567…c954

0x34b655…2a6f

2 touches
0 conflicts

0x2379307f…8e28

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

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity