← previous blocknext block →recent activity

Analyzing

Block #74,377,213

28 transactions · 22 stateful · 2026-05-13 18:46:56 UTC

Parallelism

68/100

Blocked

55%

Avg conflicts / tx

1.21

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #74,377,213  ·  28 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xa94cf3f4…554c

0x8d66a4…3095

6 touches
3 conflicts

0x8a35acfb…d1a9

0x8d66a4…3095

6 touches
3 conflicts

0x6737ee07…9978

0x34b655…2a6f

6 touches
3 conflicts

0x62d080e9…4a7c

0x34b655…2a6f

6 touches
3 conflicts

0xb38cd031…137d

0xd32edf…ff58

5 touches
3 conflicts

0x157e8320…c3b8

0x34b655…2a6f

4 touches
1 conflict

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity