← previous blocknext block →recent activity

Analyzing

Block #72,285,729

16 transactions · 13 stateful · 2026-05-04 02:25:20 UTC

Parallelism

81/100

Blocked

38%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #72,285,729  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x08943ea2…ed03

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0x659bd0…a9da

4 touches
1 conflict

0x00000000…0001

0x659bd0…a9da

4 touches
1 conflict

0x66aa7822…997d

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0x8d66a4…3095

4 touches
1 conflict

0x7e28e55c…d05c

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x60f7fbaf…bd58

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: 0x754704bc…afb603

1 conflict on slot 0x08943ea26c…67ed03

← previous block·next block →recent activity