← previous blocknext block →recent activity

Analyzing

Block #73,532,761

18 transactions · 15 stateful · 2026-05-09 20:49:13 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.28

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,532,761  ·  18 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

0xae69c125…2379

0x2a68ba…90c5

4 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

4 touches
1 conflict

0x0175b7a6…1db9

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dba

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbb

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbc

0x6c4bfa…a540

4 touches
1 conflict

0x0175b7a6…1dbd

0x6c4bfa…a540

4 touches
1 conflict

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