← previous blocknext block →recent activity

Analyzing

Block #74,338,100

40 transactions · 29 stateful · 2026-05-13 14:26:48 UTC

Parallelism

70/100

Blocked

62%

Avg conflicts / tx

1.95

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,338,100  ·  40 txs across 12 waves  ·  depth 12
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

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

0x186f97cc…4918

0xd32edf…ff58

23 touches
66 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0xffe431af…8faa

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0029

0x1b6862…e19c

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: 0xd32edf66…9fff58

66 conflicts on slot 0x186f97cc2e…724918

← previous block·next block →recent activity