← previous blocknext block →recent activity

Analyzing

Block #74,772,318

31 transactions · 20 stateful · 2026-05-15 14:47:34 UTC

Parallelism

81/100

Blocked

45%

Avg conflicts / tx

0.65

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,772,318  ·  31 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

0x067186e4…56bb

0xd32edf…ff58

11 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0xf34802b3…9f0f

0x1b6862…e19c

4 touches
1 conflict

0xce2b6650…ecc3

0x5c2513…7777

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x00000000…0000

0xcc67aa…c71c

4 touches
1 conflict

0x00000000…0001

0xcc67aa…c71c

4 touches
1 conflict

0x00000000…0012

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

15 conflicts on slot 0x067186e40f…ea56bb

← previous block·next block →recent activity