← previous blocknext block →recent activity

Analyzing

Block #73,671,186

14 transactions · 9 stateful · 2026-05-10 12:14:00 UTC

Parallelism

86/100

Blocked

11%

Avg conflicts / tx

0.07

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,671,186  ·  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

0xea02471d…1542

0x34b655…2a6f

4 touches
1 conflict

0xf2438038…5fa7

0x34b655…2a6f

4 touches
1 conflict

0x9a43401f…9d06

0x34b655…2a6f

4 touches
1 conflict

0xc875b8db…299f

0x34b655…2a6f

4 touches
1 conflict

0x4073012d…87f9

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

2 touches
0 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

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: Perpl

1 conflict on slot 0xea02471df2…601542

← previous block·next block →recent activity