← previous blocknext block →recent activity

Analyzing

Block #73,683,305

9 transactions · 8 stateful · 2026-05-10 13:35:59 UTC

Parallelism

78/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,683,305  ·  9 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

0x00bac013…a28c

0xfd44b3…00d1

4 touches
1 conflict

0xb6b74ae0…8d5e

0xea1b8e…c5ec

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0xb8a0b1ac…1f03

0x1efe02…37d6

2 touches
0 conflicts

0x1b9e654e…0a08

0x34b655…2a6f

2 touches
0 conflicts

0x273d80cd…9ecc

0x34b655…2a6f

2 touches
0 conflicts

0x313f2565…5b00

0x34b655…2a6f

2 touches
0 conflicts

0x3702b140…97ea

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: 0xfd44b351…7f00d1

1 conflict on slot 0x00bac0131a…bba28c

← previous block·next block →recent activity