Block #73,360,283

← previous blocknext block →recent activity

Analyzing

Block #73,360,283

13 transactions · 10 stateful · 2026-05-09 01:41:34 UTC

Parallelism

77/100

Blocked

20%

Avg conflicts / tx

0.23

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,360,283  ·  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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xbdff944d…447e

0x2a68ba…90c5

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x6cb0290a…7fe8

0x065c9d…c394

2 touches
0 conflicts

0xd265e8d6…1c9f

0x065c9d…c394

2 touches
0 conflicts

0x43f02fe0…f464

0x1b6862…e19c

2 touches
0 conflicts

0x7914e964…8fdb

0x1b6862…e19c

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