← previous blocknext block →recent activity

Analyzing

Block #74,926,072

28 transactions · 15 stateful · 2026-05-16 07:53:23 UTC

Parallelism

64/100

Blocked

60%

Avg conflicts / tx

1.61

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #74,926,072  ·  28 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x6d1c2966…353b

0xd32edf…ff58

19 touches
45 conflicts

0x09000000…0007

0x000000…1000

2 touches
0 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x00000000…0000

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0002

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0003

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…000a

0x116e7d…d8f1

2 touches
0 conflicts

0x00000000…0005

0x1397bd…f779

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

45 conflicts on slot 0x6d1c296630…8c353b

← previous block·next block →recent activity