← previous blocknext block →recent activity

Analyzing

Block #73,869,101

30 transactions · 25 stateful · 2026-05-11 10:23:52 UTC

Parallelism

47/100

Blocked

72%

Avg conflicts / tx

4.2

Longest chain

16 deep

Execution timeline

did this block parallelize well?

view

block #73,869,101  ·  30 txs across 16 waves  ·  depth 16
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

wave w14

wave w15

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…0007

0x1414f3…5137

32 touches
120 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xba5743c7…21bf

0x1b6862…e19c

4 touches
1 conflict

0xb159af88…a9e7

0x065c9d…c394

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

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: 0x1414f3ba…045137

120 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity