← previous blocknext block →recent activity

Analyzing

Block #72,974,792

16 transactions · 15 stateful · 2026-05-07 06:56:43 UTC

Parallelism

56/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #72,974,792  ·  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

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x70b2f813…783c

0x2a68ba…90c5

8 touches
6 conflicts

0x8b41ec8f…c2d9

0x1b6862…e19c

8 touches
6 conflicts

0x05445272…5720

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

6 touches
3 conflicts

0x0b390c61…dc07

0x065c9d…c394

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

6 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity