← previous blocknext block →recent activity

Analyzing

Block #73,975,299

13 transactions · 9 stateful · 2026-05-11 22:11:09 UTC

Parallelism

77/100

Blocked

22%

Avg conflicts / tx

0.15

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,975,299  ·  13 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

0x243344bd…0b8c

0x34b655…2a6f

4 touches
1 conflict

0x35b85d8e…1edd

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x7f430e47…4cbd

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1aa

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

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

1 conflict on slot 0x243344bdf7…0e0b8c

← previous block·next block →recent activity