← previous blocknext block →recent activity

Analyzing

Block #73,343,800

19 transactions · 16 stateful · 2026-05-08 23:51:59 UTC

Parallelism

84/100

Blocked

19%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,343,800  ·  19 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

6 touches
3 conflicts

0xd821ae10…fe17

0xc8689a…ee79

6 touches
3 conflicts

0x107c9d8c…097f

0x065c9d…c394

4 touches
3 conflicts

0x554f1ada…6916

0xaba216…a862

4 touches
2 conflicts

0x0175b7a6…1dba

0xaba216…a862

4 touches
1 conflict

0x2e2214a9…fe0d

0xaba216…a862

4 touches
1 conflict

0x6f08361d…bda6

0x065c9d…c394

4 touches
1 conflict

0x8d0dfe2c…3345

0x2a68ba…90c5

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

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity