Block #72,296,193

← previous blocknext block →recent activity

Analyzing

Block #72,296,193

6 transactions · 6 stateful · 2026-05-04 03:35:36 UTC

Parallelism

67/100

Blocked

17%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,296,193  ·  6 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

0xc4ecec0b…3822

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8d75388d…0bd1

0x065c9d…c394

3 touches
1 conflict

0x6bef1798…7e0a

0x065c9d…c394

3 touches
1 conflict

0x31c807fb…01ed

0x065c9d…c394

2 touches
0 conflicts

0x83fff0fb…b4aa

0x065c9d…c394

2 touches
0 conflicts

0xbbee74c2…567a

0x065c9d…c394

2 touches
0 conflicts

0xdaff5a5b…0740

0x065c9d…c394

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 0xc4ecec0b90…ab3822

← previous block·next block →recent activity