← previous blocknext block →recent activity

Analyzing

Block #73,478,202

16 transactions · 14 stateful · 2026-05-09 14:46:17 UTC

Parallelism

63/100

Blocked

36%

Avg conflicts / tx

0.94

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,478,202  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x81a7ba4d…8c4b

0x23c26b…7777

12 touches
15 conflicts

0x08fdca0b…4abf

0x3bd359…433a

12 touches
15 conflicts

0x00000000…0000

0xfdc9ea…8789

12 touches
15 conflicts

0x00000000…0001

0xfdc9ea…8789

12 touches
15 conflicts

0x00000000…0003

0xfdc9ea…8789

12 touches
15 conflicts

0x00000000…0004

0x5afd3e…7620

2 touches
0 conflicts

0x8f4e01d5…1715

0x5afd3e…7620

2 touches
0 conflicts

0xba1e387c…f432

0x5afd3e…7620

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: 0x23c26bd5…547777

15 conflicts on slot 0x81a7ba4dd6…568c4b

← previous block·next block →recent activity