← previous blocknext block →recent activity

Analyzing

Block #73,297,604

16 transactions · 11 stateful · 2026-05-08 18:44:37 UTC

Parallelism

88/100

Blocked

9%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,297,604  ·  16 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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8e76bd39…a1de

0x34b655…2a6f

4 touches
1 conflict

0xa15427f6…d932

0x34b655…2a6f

4 touches
1 conflict

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0x0980c178…e0e7

0x065c9d…c394

2 touches
0 conflicts

0x6f08361d…bda6

0x065c9d…c394

2 touches
0 conflicts

0x9160c9fb…b341

0x065c9d…c394

2 touches
0 conflicts

0xf537eaa0…73c8

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: 0x34b6552d…112a6f

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity