Block #71,744,263

← previous blocknext block →recent activity

Analyzing

Block #71,744,263

13 transactions · 10 stateful · 2026-05-01 14:13:10 UTC

Parallelism

85/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,744,263  ·  13 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

0x4f4bdabd…ffba

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xeeb38aa7…8f00

0x34b655…2a6f

4 touches
1 conflict

0xf3981be5…2c47

0x34b655…2a6f

4 touches
1 conflict

0x0d3d3160…bb17

0x34b655…2a6f

4 touches
1 conflict

0x065675de…3e7b

0x065c9d…c394

2 touches
0 conflicts

0x0ed87692…8bcc

0x065c9d…c394

2 touches
0 conflicts

0x65d65a0a…a48d

0x065c9d…c394

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

1 conflict on slot 0x4f4bdabdf3…ecffba

← previous block·next block →recent activity