← previous blocknext block →recent activity

Analyzing

Block #74,283,751

29 transactions · 20 stateful · 2026-05-13 08:25:11 UTC

Parallelism

55/100

Blocked

65%

Avg conflicts / tx

2.72

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #74,283,751  ·  29 txs across 13 waves  ·  depth 13
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

wave w12

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

0xdc80ae12…753a

0xd32edf…ff58

25 touches
78 conflicts

0xaa3e5ab2…fd8a

0x3bd359…433a

4 touches
1 conflict

0x44ad89ba…cf83

0x7131ec…7777

4 touches
1 conflict

0xa472d565…9fe4

0x3bd359…433a

4 touches
1 conflict

0x00000000…0000

0xc82b5c…bb3a

4 touches
1 conflict

0x00000000…0001

0xc82b5c…bb3a

4 touches
1 conflict

0xd46cd782…e7f2

0x7131ec…7777

4 touches
1 conflict

0xab2f6eed…254a

0x188d58…ea8e

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

78 conflicts on slot 0xdc80ae12cf…fc753a

← previous block·next block →recent activity