← previous blocknext block →recent activity

Analyzing

Block #72,296,659

25 transactions · 18 stateful · 2026-05-04 03:38:42 UTC

Parallelism

64/100

Blocked

56%

Avg conflicts / tx

1.68

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #72,296,659  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x82d6adfd…e57d

0xd32edf…ff58

17 touches
36 conflicts

0x17606ba6…1b6e

0x754704…b603

6 touches
3 conflicts

0x01e7b865…6e6f

0x188d58…ea8e

4 touches
1 conflict

0x00000000…0000

0x63e48b…53f2

4 touches
1 conflict

0x01e7b865…6e6d

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a566

0x188d58…ea8e

4 touches
1 conflict

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0xf6cc7de8…0b4a

0x3bd359…433a

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: 0xd32edf66…9fff58

36 conflicts on slot 0x82d6adfd09…a9e57d

← previous block·next block →recent activity