Block #71,643,188

← previous blocknext block →recent activity

Analyzing

Block #71,643,188

17 transactions · 17 stateful · 2026-05-01 03:00:10 UTC

Parallelism

88/100

Blocked

18%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,643,188  ·  17 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

0xea57afd0…4232

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0x7e9d3a…9fda

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xa1869cb0…ee22

0x065c9d…c394

2 touches
0 conflicts

0xd88dc7df…9c11

0x065c9d…c394

2 touches
0 conflicts

0xfe2bac2b…2cec

0x065c9d…c394

2 touches
0 conflicts

0xd74d5bed…5e7e

0x2a68ba…90c5

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 0xea57afd097…7f4232

← previous block·next block →recent activity