← previous blocknext block →recent activity

Analyzing

Block #73,014,243

15 transactions · 12 stateful · 2026-05-07 11:19:20 UTC

Parallelism

80/100

Blocked

33%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,014,243  ·  15 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xdaca243a…f9de

0x34b655…2a6f

6 touches
3 conflicts

0xcc6521c1…c892

0x8d66a4…3095

4 touches
1 conflict

0x1eb0fab5…3517

0x34b655…2a6f

4 touches
1 conflict

0x4599ceea…e18c

0x34b655…2a6f

4 touches
1 conflict

0x55968d29…1d6a

0x34b655…2a6f

4 touches
1 conflict

0x65e795ca…0320

0x34b655…2a6f

4 touches
1 conflict

0xc64d5398…d2e5

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: 0x34b6552d…112a6f

3 conflicts on slot 0xea02471df2…601542

← previous block·next block →recent activity