← previous blocknext block →recent activity

Analyzing

Block #74,463,643

17 transactions · 17 stateful · 2026-05-14 04:22:23 UTC

Parallelism

59/100

Blocked

59%

Avg conflicts / tx

1.41

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #74,463,643  ·  17 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

0xf3981be5…2c47

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xea02471d…1542

0x34b655…2a6f

8 touches
6 conflicts

0xbb12db23…857e

0x34b655…2a6f

7 touches
6 conflicts

0x00000000…0001

0xcc67aa…c71c

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x79d53a28…6a9e

0x34b655…2a6f

6 touches
3 conflicts

0x00c46468…f328

0x3bd359…433a

6 touches
3 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

15 conflicts on slot 0xf3981be56e…f02c47

← previous block·next block →recent activity