← previous blocknext block →recent activity

Analyzing

Block #73,043,068

16 transactions · 15 stateful · 2026-05-07 14:31:10 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,043,068  ·  16 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

0x8fb0fecf…cb2f

0x34b655…2a6f

4 touches
1 conflict

0xa7a586ac…c700

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x2877f440…c2c8

0x34b655…2a6f

4 touches
1 conflict

0x388e001a…7e04

0x34b655…2a6f

4 touches
1 conflict

0x00d1f9f0…0211

0x1efe02…37d6

2 touches
0 conflicts

0x2b4e1915…8a3a

0x1efe02…37d6

2 touches
0 conflicts

0x64570584…d48a

0x1efe02…37d6

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 0x8fb0fecfbf…98cb2f

← previous block·next block →recent activity