← previous blocknext block →recent activity

Analyzing

Block #72,286,174

14 transactions · 11 stateful · 2026-05-04 02:28:19 UTC

Parallelism

86/100

Blocked

18%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,286,174  ·  14 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x74e71984…ae90

0x2a68ba…90c5

4 touches
1 conflict

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0x59776396…43c6

0xd32edf…ff58

3 touches
1 conflict

0x09075329…ea22

0x065c9d…c394

3 touches
1 conflict

0xacb92b05…9613

0x065c9d…c394

3 touches
1 conflict

0xcedf7cf4…1c7c

0x065c9d…c394

3 touches
1 conflict

0xf0f673fd…37a7

0x8d0464…4402

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: 0x065c9d28…a9c394

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity