Block #71,094,647

← previous blocknext block →recent activity

Analyzing

Block #71,094,647

19 transactions · 16 stateful · 2026-04-28 14:03:08 UTC

Parallelism

89/100

Blocked

19%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,094,647  ·  19 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

0x4ab14837…e1b2

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…000b

0x24b8be…7f9e

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x37e1be01…6f19

0x54cd53…9e7d

2 touches
0 conflicts

0xa27fa22d…7dca

0x54cd53…9e7d

2 touches
0 conflicts

0xd1a0adf6…6e55

0x54cd53…9e7d

2 touches
0 conflicts

0x049f2314…3b61

0x6657d1…8ccc

2 touches
0 conflicts

0x08abfabe…4041

0x6657d1…8ccc

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: 0x2a68ba18…8e90c5

1 conflict on slot 0x4ab14837eb…ffe1b2

← previous block·next block →recent activity