← previous blocknext block →recent activity

Analyzing

Block #73,598,846

12 transactions · 9 stateful · 2026-05-10 04:08:17 UTC

Parallelism

83/100

Blocked

22%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,598,846  ·  12 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

0xac206e47…ef7d

0x34b655…2a6f

4 touches
1 conflict

0xcc8f294b…ddcb

0x34b655…2a6f

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x8240d70c…7c3b

0x34b655…2a6f

4 touches
1 conflict

0x97a7a85c…ba1b

0x065c9d…c394

2 touches
0 conflicts

0xaef3a67e…7f7a

0x065c9d…c394

2 touches
0 conflicts

0xbae41934…a92b

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 0xac206e4761…ffef7d

← previous block·next block →recent activity