← previous blocknext block →recent activity

Analyzing

Block #73,050,944

28 transactions · 22 stateful · 2026-05-07 15:23:41 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,050,944  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…0002

0xab3526…fa38

22 touches
55 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x042cebb9…1487

0x57ea24…2cec

2 touches
0 conflicts

0x12a42c77…f432

0x57ea24…2cec

2 touches
0 conflicts

0x15abeaf6…e083

0x57ea24…2cec

2 touches
0 conflicts

0x15bae5fc…9f7e

0x57ea24…2cec

2 touches
0 conflicts

0x2c650388…78f7

0x57ea24…2cec

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: 0xab35264b…1cfa38

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity