← previous blocknext block →recent activity

Analyzing

Block #73,677,546

10 transactions · 8 stateful · 2026-05-10 12:57:05 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,677,546  ·  10 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

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x3ded8a5b…3cf0

0x34b655…2a6f

4 touches
1 conflict

0x487e880c…650b

0x34b655…2a6f

4 touches
1 conflict

0x06ba6aa3…ef21

0x065c9d…c394

2 touches
0 conflicts

0x2e5f9549…d6e5

0x065c9d…c394

2 touches
0 conflicts

0x38f1db62…53ed

0x065c9d…c394

2 touches
0 conflicts

0x49f5c127…52b7

0x065c9d…c394

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 0xf2438038b6…475fa7

← previous block·next block →recent activity