← previous blocknext block →recent activity

Analyzing

Block #74,352,801

14 transactions · 11 stateful · 2026-05-13 16:04:27 UTC

Parallelism

86/100

Blocked

9%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #74,352,801  ·  14 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

0xe5e7089a…fb91

0x34b655…2a6f

4 touches
1 conflict

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x9e719c7a…df63

0x34b655…2a6f

3 touches
1 conflict

0xd40bddc1…773c

0x34b655…2a6f

3 touches
1 conflict

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

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 0xe5e7089a63…bcfb91

← previous block·next block →recent activity