← previous blocknext block →recent activity

Analyzing

Block #73,869,207

21 transactions · 18 stateful · 2026-05-11 10:24:34 UTC

Parallelism

38/100

Blocked

72%

Avg conflicts / tx

3.76

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #73,869,207  ·  21 txs across 13 waves  ·  depth 13
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

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

26 touches
78 conflicts

0x8a2657f5…e008

0x34b655…2a6f

4 touches
1 conflict

0x15d039e7…4bb6

0x34b655…2a6f

4 touches
1 conflict

0x3f0dfd32…5bcd

0x1414f3…5137

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0013

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0015

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

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

78 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity