← previous blocknext block →recent activity

Analyzing

Block #73,976,025

27 transactions · 19 stateful · 2026-05-11 22:16:03 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.59

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,976,025  ·  27 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…0015

0x1b6862…e19c

8 touches
6 conflicts

0x3af0dd8e…0023

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0013

0x1b6862…e19c

8 touches
6 conflicts

0x656dfd34…20c9

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x0d0b2509…074d

0x3bd359…433a

6 touches
3 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: 0x1b68626d…2de19c

6 conflicts on slot 0x0000000000…000015

← previous block·next block →recent activity