Block #70,996,823

← previous blocknext block →recent activity

Analyzing

Block #70,996,823

10 transactions · 9 stateful · 2026-04-28 03:11:46 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #70,996,823  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x462c8be7…4f83

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1af

0x8d66a4…3095

4 touches
1 conflict

0x8a35acfb…d1b0

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x3258ac13…a315

0x065c9d…c394

4 touches
1 conflict

0x43f82aaa…2593

0x065c9d…c394

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: 0x8d66a43f…113095

1 conflict on slot 0x462c8be7ee…684f83

← previous block·next block →recent activity