← previous blocknext block →recent activity

Analyzing

Block #72,498,716

35 transactions · 28 stateful · 2026-05-05 02:04:43 UTC

Parallelism

83/100

Blocked

54%

Avg conflicts / tx

0.97

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,498,716  ·  35 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…0002

0x7e9d3a…9fda

12 touches
15 conflicts

0xf3981be5…2c47

0x34b655…2a6f

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0xe89e1a22…ce49

0x8d66a4…3095

6 touches
3 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x143dba04…1b98

0x8d66a4…3095

6 touches
3 conflicts

0x1e451306…7993

0x8d66a4…3095

6 touches
3 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: 0x7e9d3a8a…4f9fda

15 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity