← previous blocknext block →recent activity

Analyzing

Block #73,470,386

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

Parallelism

56/100

Blocked

56%

Avg conflicts / tx

1.83

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,470,386  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0xc6e1c41a…026a

0x065c9d…c394

6 touches
3 conflicts

0x6fd5b9aa…c4e8

0x065c9d…c394

4 touches
2 conflicts

0xfe0483cb…686c

0x065c9d…c394

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity