← previous blocknext block →recent activity

Analyzing

Block #74,418,941

15 transactions · 13 stateful · 2026-05-13 23:24:42 UTC

Parallelism

26/100

Blocked

77%

Avg conflicts / tx

3.67

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #74,418,941  ·  15 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xfcdba3b0…cfc2

0x3bd359…433a

22 touches
55 conflicts

0x00000000…0000

0xf4e40a…28ea

22 touches
55 conflicts

0x00000000…0002

0xf4e40a…28ea

22 touches
55 conflicts

0x00000000…0003

0xf4e40a…28ea

22 touches
55 conflicts

0xd352f775…a505

0x39b9e0…7777

22 touches
55 conflicts

0x1bf4abb8…3a9e

0x39b9e0…7777

2 touches
0 conflicts

0x73a69d96…939d

0x39b9e0…7777

2 touches
0 conflicts

0x937d187e…e650

0x39b9e0…7777

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: 0x3bd359c1…15433a

55 conflicts on slot 0xfcdba3b0d5…f1cfc2

← previous block·next block →recent activity