← previous blocknext block →recent activity

Analyzing

Block #73,611,191

8 transactions · 7 stateful · 2026-05-10 05:30:22 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,611,191  ·  8 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

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x07e1d521…fc32

0x34b655…2a6f

2 touches
0 conflicts

0x23b2399c…6e4b

0x34b655…2a6f

2 touches
0 conflicts

0x2fad73a1…ae09

0x34b655…2a6f

2 touches
0 conflicts

0x375b6201…9c1e

0x34b655…2a6f

2 touches
0 conflicts

0x40306b54…5ae8

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1aa

← previous block·next block →recent activity