← previous blocknext block →recent activity

Analyzing

Block #73,359,935

10 transactions · 9 stateful · 2026-05-09 01:39:14 UTC

Parallelism

70/100

Blocked

22%

Avg conflicts / tx

0.2

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,359,935  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x99d5ffa1…4059

0x34b655…2a6f

4 touches
1 conflict

0xad0fa15c…e45b

0x34b655…2a6f

4 touches
1 conflict

0xb00dc068…3f0b

0x34b655…2a6f

4 touches
1 conflict

0xb81d3ee7…3947

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xf06c2cf5…61bd

0x34b655…2a6f

4 touches
1 conflict

0x33f2d9b1…b689

0x34b655…2a6f

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 0x8240d70c8a…f27c3b

← previous block·next block →recent activity