← previous blocknext block →recent activity

Analyzing

Block #73,748,824

22 transactions · 12 stateful · 2026-05-10 20:57:58 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,748,824  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0xe96c91d2…32ff

0x8d66a4…3095

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

4 touches
1 conflict

0x908d4442…2c4b

0x34b655…2a6f

4 touches
1 conflict

0x9753c6ec…6479

0x34b655…2a6f

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0xab41bf9c…66a9

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x8a35acfbc1…6bd1ad

← previous block·next block →recent activity