← previous blocknext block →recent activity

Analyzing

Block #73,869,187

27 transactions · 25 stateful · 2026-05-11 10:24:26 UTC

Parallelism

33/100

Blocked

72%

Avg conflicts / tx

5.7

Longest chain

18 deep

Execution timeline

did this block parallelize well?

view

block #73,869,187  ·  27 txs across 18 waves  ·  depth 18
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

wave w16

wave w17

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

36 touches
153 conflicts

0x4f483049…3cc7

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x1e024506…a786

0x065c9d…c394

2 touches
0 conflicts

0x7d241c2a…08b0

0x065c9d…c394

2 touches
0 conflicts

0x9f3a9358…5d3b

0x065c9d…c394

2 touches
0 conflicts

0xb159af88…a9e7

0x065c9d…c394

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

153 conflicts on slot 0x0000000000…000007

← previous block·next block →recent activity