← previous blocknext block →recent activity

Analyzing

Block #71,243,080

6 transactions · 5 stateful · 2026-04-29 06:31:08 UTC

Parallelism

67/100

Blocked

20%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,243,080  ·  6 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

0x0f79c210…26e3

0x065c9d…c394

4 touches
1 conflict

0x92444c5f…11b7

0x065c9d…c394

4 touches
1 conflict

0x27055591…3a20

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd8d59b0c…1d0b

0x065c9d…c394

4 touches
1 conflict

0xb6fabee1…c7ee

0x065c9d…c394

2 touches
1 conflict

0xb6fabee1…c7ef

0x065c9d…c394

2 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: 0x065c9d28…a9c394

1 conflict on slot 0x0f79c210a2…8d26e3

← previous block·next block →recent activity