Block #72,098,194

← previous blocknext block →recent activity

Analyzing

Block #72,098,194

8 transactions · 6 stateful · 2026-05-03 05:29:25 UTC

Parallelism

75/100

Blocked

17%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #72,098,194  ·  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

0x143dba04…1b98

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ad

0x8d66a4…3095

4 touches
1 conflict

0xe89e1a22…ce49

0x8d66a4…3095

4 touches
1 conflict

0x75f928fc…0465

0x34b655…2a6f

2 touches
0 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

2 touches
0 conflicts

0xfadc118d…5d64

0x34b655…2a6f

2 touches
0 conflicts

0xfe3d37ee…6e67

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 0x143dba04c2…a61b98

← previous block·next block →recent activity