← previous blocknext block →recent activity

Analyzing

Block #74,440,451

12 transactions · 11 stateful · 2026-05-14 01:47:57 UTC

Parallelism

42/100

Blocked

64%

Avg conflicts / tx

1.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,440,451  ·  12 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x00000000…0002

0xab3526…fa38

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xadac4a86…c2bc

0x34b655…2a6f

4 touches
1 conflict

0x0b6d25a1…2e3b

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x38dee07f…7598

0x34b655…2a6f

2 touches
0 conflicts

0xa486f342…64d5

0x34b655…2a6f

2 touches
0 conflicts

0xb245fe36…d765

0x34b655…2a6f

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: 0xab35264b…1cfa38

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity