Block #72,296,300

← previous blocknext block →recent activity

Analyzing

Block #72,296,300

24 transactions · 18 stateful · 2026-05-04 03:36:19 UTC

Parallelism

67/100

Blocked

50%

Avg conflicts / tx

1.42

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #72,296,300  ·  24 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa10d36a7…5577

0xd32edf…ff58

15 touches
28 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

6 touches
3 conflicts

0xbbee74c2…567a

0x065c9d…c394

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0xc394e7d5…6681

0x065c9d…c394

3 touches
1 conflict

0x9c059d10…b022

0x065c9d…c394

3 touches
1 conflict

0x74c01f97…9b77

0x065c9d…c394

3 touches
1 conflict

0xd5daadcc…c9b9

0x2a3755…a5a6

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

28 conflicts on slot 0xa10d36a76d…035577

← previous block·next block →recent activity