← previous blocknext block →recent activity

Analyzing

Block #74,359,576

13 transactions · 6 stateful · 2026-05-13 16:49:33 UTC

Parallelism

85/100

Blocked

17%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,359,576  ·  13 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x62d080e9…4a7c

0x34b655…2a6f

4 touches
1 conflict

0x35019383…fc7d

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0711ec2d…d973

0x34b655…2a6f

2 touches
0 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x36f4b4f0…0188

0x34b655…2a6f

2 touches
0 conflicts

0x4f483049…3cc7

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 0x62d080e928…5a4a7c

← previous block·next block →recent activity