Block #72,399,890

← previous blocknext block →recent activity

Analyzing

Block #72,399,890

15 transactions · 11 stateful · 2026-05-04 15:06:29 UTC

Parallelism

87/100

Blocked

27%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,399,890  ·  15 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

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0x7186c17e…02ee

0xd32edf…ff58

3 touches
1 conflict

0x05af060c…3543

0x065c9d…c394

2 touches
0 conflicts

0x3af3f9e9…717e

0x065c9d…c394

2 touches
0 conflicts

0x4ba1fda1…2acc

0x065c9d…c394

2 touches
0 conflicts

0x7abf1904…b003

0x065c9d…c394

2 touches
0 conflicts

0x897b34fc…f9a1

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 0x0000000000…00003d

← previous block·next block →recent activity