Block #71,555,841

← previous blocknext block →recent activity

Analyzing

Block #71,555,841

40 transactions · 30 stateful · 2026-04-30 17:18:49 UTC

Parallelism

73/100

Blocked

57%

Avg conflicts / tx

1.8

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #71,555,841  ·  40 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…0002

0x7e9d3a…9fda

22 touches
55 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xbc04d98e…a484

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0x67813250…9467

0xb744f5…7777

4 touches
1 conflict

0x51500297…20aa

0x34b655…2a6f

4 touches
1 conflict

0x676f9f01…a8ac

0x34b655…2a6f

4 touches
1 conflict

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: 0x7e9d3a8a…4f9fda

55 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity