← previous blocknext block →recent activity

Analyzing

Block #73,651,441

15 transactions · 12 stateful · 2026-05-10 10:00:51 UTC

Parallelism

53/100

Blocked

50%

Avg conflicts / tx

1.2

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,651,441  ·  15 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xb159af88…a9e7

0x065c9d…c394

8 touches
6 conflicts

0x65c47b7f…94bf

0x065c9d…c394

3 touches
1 conflict

0xbd1155f5…e484

0x065c9d…c394

3 touches
1 conflict

0x87c54585…529f

0x065c9d…c394

3 touches
1 conflict

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 conflicts

0x1a4b4152…0a08

0x6c4bfa…a540

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

10 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity