Block #70,892,173

← previous blocknext block →recent activity

Analyzing

Block #70,892,173

22 transactions · 21 stateful · 2026-04-27 15:34:46 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

1.36

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #70,892,173  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xb857c1…9be1

16 touches
28 conflicts

0x8956cb26…42fa

0x73ada1…8be0

4 touches
1 conflict

0xf4e554ca…1a6c

0x73ada1…8be0

4 touches
1 conflict

0x1b4df54f…7afb

0x754704…b603

4 touches
1 conflict

0xa3dc6f35…13e9

0x754704…b603

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xeeb38aa7…8f00

0x34b655…2a6f

4 touches
1 conflict

0x09000000…0001

0x000000…1000

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: 0xb857c13a…1a9be1

28 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity