Block #72,094,631

← previous blocknext block →recent activity

Analyzing

Block #72,094,631

6 transactions · 4 stateful · 2026-05-03 05:05:42 UTC

Parallelism

67/100

Blocked

25%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,094,631  ·  6 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x5138188e…796b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xc08384da…ecb7

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x2efd1e50…71e3

0x065c9d…c394

2 touches
0 conflicts

0x5365b3c9…d687

0x065c9d…c394

2 touches
0 conflicts

0xad5f0940…e334

0x065c9d…c394

2 touches
0 conflicts

0xb616ad12…0f16

0x065c9d…c394

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

1 conflict on slot 0x5138188e69…d6796b

← previous block·next block →recent activity