Block #71,744,258

← previous blocknext block →recent activity

Analyzing

Block #71,744,258

13 transactions · 11 stateful · 2026-05-01 14:13:08 UTC

Parallelism

85/100

Blocked

9%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

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

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x15c9b5bf…f732

0x34b655…2a6f

4 touches
1 conflict

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x0add7de1…8b7c

0x57ea24…2cec

2 touches
0 conflicts

0x12a42c77…f432

0x57ea24…2cec

2 touches
0 conflicts

0x14873a25…9a37

0x57ea24…2cec

2 touches
0 conflicts

0x15bae5fc…9f7e

0x57ea24…2cec

2 touches
0 conflicts

0x39466218…cb6b

0x57ea24…2cec

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity