Block #73,343,713

← previous blocknext block →recent activity

Analyzing

Block #73,343,713

16 transactions · 13 stateful · 2026-05-08 23:51:24 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,343,713  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x0c3cca62…01f5

0xd32edf…ff58

9 touches
10 conflicts

0xf537eaa0…73c8

0x065c9d…c394

4 touches
1 conflict

0x00000000…0000

0x036056…1881

2 touches
0 conflicts

0x3e8a4a5c…5929

0x036056…1881

2 touches
0 conflicts

0xa6705fe7…a45a

0x036056…1881

2 touches
0 conflicts

0xefb186a4…a12b

0x036056…1881

2 touches
0 conflicts

0x5745bc1e…4234

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0007

0x09f880…ede0

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

10 conflicts on slot 0x0c3cca62bc…7101f5

← previous block·next block →recent activity