← previous blocknext block →recent activity

Analyzing

Block #74,691,236

29 transactions · 22 stateful · 2026-05-15 05:45:39 UTC

Parallelism

72/100

Blocked

68%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #74,691,236  ·  29 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x1b6862…e19c

16 touches
28 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

16 touches
28 conflicts

0x6fd9ae7c…e97d

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0028

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0012

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0013

0x1b6862…e19c

16 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

16 touches
28 conflicts

0x31ed7cd7…ee20

0xd32edf…ff58

15 touches
28 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

28 conflicts on slot 0x0000000000…000018

← previous block·next block →recent activity