← previous blocknext block →recent activity

Analyzing

Block #73,688,683

13 transactions · 10 stateful · 2026-05-10 14:12:10 UTC

Parallelism

77/100

Blocked

30%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,688,683  ·  13 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

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x6fd9ae7c…e981

0x1b6862…e19c

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x525bef63…71fa

0xd32edf…ff58

3 touches
1 conflict

0x00000000…002c

0x1b6862…e19c

2 touches
0 conflicts

0x09000000…0001

0x000000…1000

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: 0x754704bc…afb603

1 conflict on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity