← previous blocknext block →recent activity

Analyzing

Block #72,994,165

10 transactions · 7 stateful · 2026-05-07 09:05:52 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,994,165  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…000d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001e

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0016

0x1b6862…e19c

2 touches
0 conflicts

0xbf9c3d22…aa5b

0x1b6862…e19c

2 touches
0 conflicts

0xd897dd17…055e

0x1b6862…e19c

2 touches
0 conflicts

0x388e001a…7e04

0x34b655…2a6f

2 touches
0 conflicts

0x5d70606a…1d53

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: 0x1b68626d…2de19c

1 conflict on slot 0x0000000000…00000d

← previous block·next block →recent activity