← previous blocknext block →recent activity

Analyzing

Block #74,436,343

33 transactions · 20 stateful · 2026-05-14 01:20:36 UTC

Parallelism

64/100

Blocked

65%

Avg conflicts / tx

2.06

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #74,436,343  ·  33 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x07cfd7a1…777d

0xd32edf…ff58

23 touches
66 conflicts

0x99bd7b88…4427

0x350035…7777

4 touches
1 conflict

0x12fb62e3…d437

0x3bd359…433a

4 touches
1 conflict

0xb7143610…adc4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0x573903…4229

4 touches
1 conflict

0x00000000…0003

0x573903…4229

4 touches
1 conflict

0x00000000…0004

0x573903…4229

4 touches
1 conflict

0x00000000…0003

0x116e7d…d8f1

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

66 conflicts on slot 0x07cfd7a14c…a6777d

← previous block·next block →recent activity