← previous blocknext block →recent activity

Analyzing

Block #73,200,564

15 transactions · 11 stateful · 2026-05-08 07:59:07 UTC

Parallelism

87/100

Blocked

9%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,200,564  ·  15 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x2a354a63…0515

0x065c9d…c394

4 touches
1 conflict

0x09ec6da1…d7f5

0xd32edf…ff58

3 touches
1 conflict

0x8e66da19…66b6

0x065c9d…c394

2 touches
0 conflicts

0x70b2f813…783c

0x2a68ba…90c5

2 touches
0 conflicts

0xe09eda07…8dda

0x2a68ba…90c5

2 touches
0 conflicts

0xbfe7fd3a…3168

0x3bd359…433a

2 touches
0 conflicts

0x7ee0f190…c40e

0x57ea24…2cec

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