← previous blocknext block →recent activity

Analyzing

Block #73,328,495

23 transactions · 22 stateful · 2026-05-08 22:10:16 UTC

Parallelism

61/100

Blocked

55%

Avg conflicts / tx

1.87

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,328,495  ·  23 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xea101c54…dfe2

0xd32edf…ff58

17 touches
36 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

8 touches
6 conflicts

0x6f08361d…bda6

0x065c9d…c394

6 touches
3 conflicts

0x46cb45de…a567

0x188d58…ea8e

4 touches
1 conflict

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002d

0x1b6862…e19c

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: 0xd32edf66…9fff58

36 conflicts on slot 0xea101c5467…43dfe2

← previous block·next block →recent activity