← previous blocknext block →recent activity

Analyzing

Block #74,471,513

18 transactions · 16 stateful · 2026-05-14 05:14:38 UTC

Parallelism

67/100

Blocked

38%

Avg conflicts / tx

0.78

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #74,471,513  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xda1f3e2c…b73d

0x34b655…2a6f

6 touches
3 conflicts

0x10f5f4d8…572e

0x34b655…2a6f

4 touches
1 conflict

0x1dc86774…166a

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7cb2f3fa…4836

0x34b655…2a6f

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity