Block #72,498,178

← previous blocknext block →recent activity

Analyzing

Block #72,498,178

21 transactions · 18 stateful · 2026-05-05 02:01:08 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #72,498,178  ·  21 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…7212

0x34b655…2a6f

6 touches
3 conflicts

0x32aa281b…0f8e

0x34b655…2a6f

6 touches
3 conflicts

0x1179284b…db76

0x34b655…2a6f

4 touches
1 conflict

0x1c913164…5c2e

0x34b655…2a6f

4 touches
1 conflict

0x3b53436c…2ec3

0x34b655…2a6f

4 touches
1 conflict

0x578e7f66…1b56

0x34b655…2a6f

4 touches
1 conflict

0x6d0c65d9…c36f

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity