Block #72,167,273

← previous blocknext block →recent activity

Analyzing

Block #72,167,273

14 transactions · 13 stateful · 2026-05-03 13:09:20 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

0.79

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #72,167,273  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x26118226…8f5d

0x065c9d…c394

2 touches
0 conflicts

0x5c8c6ab6…dc36

0x065c9d…c394

2 touches
0 conflicts

0xfa503888…1168

0x065c9d…c394

2 touches
0 conflicts

0x544ac270…ab6b

0x3bd359…433a

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

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity