← previous blocknext block →recent activity

Analyzing

Block #74,634,301

13 transactions · 13 stateful · 2026-05-14 23:26:00 UTC

Parallelism

77/100

Blocked

23%

Avg conflicts / tx

0.31

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #74,634,301  ·  13 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0x5c8c6ab6…dc36

0x065c9d…c394

4 touches
1 conflict

0x742436a7…c4d4

0x34b655…2a6f

4 touches
1 conflict

0x4118bd12…924a

0x34b655…2a6f

4 touches
1 conflict

0x24968e6d…0132

0x065c9d…c394

2 touches
0 conflicts

0x4d602f07…584b

0x065c9d…c394

2 touches
0 conflicts

0xffe431af…8faa

0x065c9d…c394

2 touches
0 conflicts

0x23114fac…630a

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

1 conflict on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity