Block #71,244,300

← previous blocknext block →recent activity

Analyzing

Block #71,244,300

16 transactions · 12 stateful · 2026-04-29 06:39:16 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,244,300  ·  16 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

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x2b088f80…4cf9

0x34b655…2a6f

2 touches
0 conflicts

0x2e1c8214…c8c1

0x34b655…2a6f

2 touches
0 conflicts

0x404dbe6c…c67a

0x34b655…2a6f

2 touches
0 conflicts

0x664bf99e…0a8c

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 0x8a35acfbc1…6bd1ae

← previous block·next block →recent activity