Block #73,917,620

← previous blocknext block →recent activity

Analyzing

Block #73,917,620

15 transactions · 9 stateful · 2026-05-11 15:47:05 UTC

Parallelism

60/100

Blocked

56%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,917,620  ·  15 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

0x00000000…003d

0x065c9d…c394

12 touches
15 conflicts

0xf537eaa0…73c8

0x065c9d…c394

8 touches
6 conflicts

0x0d9436be…8f04

0x065c9d…c394

5 touches
3 conflicts

0xb5312b9b…34ab

0x065c9d…c394

5 touches
3 conflicts

0xf0f673fd…37a7

0x5d823e…89c6

4 touches
1 conflict

0x6b319071…a105

0xc8689a…ee79

4 touches
1 conflict

0x1a4b4152…0a08

0x5d823e…89c6

4 touches
1 conflict

0x3e4b8d9f…b8a7

0x5d823e…89c6

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: 0x065c9d28…a9c394

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity