← previous blocknext block →recent activity

Analyzing

Block #72,498,686

44 transactions · 30 stateful · 2026-05-05 02:04:31 UTC

Parallelism

82/100

Blocked

57%

Avg conflicts / tx

1.23

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,498,686  ·  44 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

16 touches
28 conflicts

0x17606ba6…1b6e

0x754704…b603

12 touches
15 conflicts

0xeed0fbcf…1a5b

0xd32edf…ff58

9 touches
10 conflicts

0x56a919c4…ab49

0xee8c0e…1242

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x1c354dc0…96de

0x754704…b603

6 touches
3 conflicts

0xcb45d9d6…cb84

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

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

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity