← previous blocknext block →recent activity

Analyzing

Block #74,283,884

12 transactions · 9 stateful · 2026-05-13 08:26:04 UTC

Parallelism

50/100

Blocked

56%

Avg conflicts / tx

1.25

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,283,884  ·  12 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

0x56a876f8…625d

0xd32edf…ff58

11 touches
15 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…0019

0x116e7d…d8f1

2 touches
0 conflicts

0xab2f6eed…254a

0x188d58…ea8e

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

15 conflicts on slot 0x56a876f8ad…d7625d

← previous block·next block →recent activity