Block #70,877,813

← previous blocknext block →recent activity

Analyzing

Block #70,877,813

7 transactions · 5 stateful · 2026-04-27 13:59:12 UTC

Parallelism

71/100

Blocked

20%

Avg conflicts / tx

0.14

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #70,877,813  ·  7 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

0x80a503f8…b088

0x065c9d…c394

4 touches
1 conflict

0x9a6f0c2d…b0bd

0x065c9d…c394

4 touches
1 conflict

0xbf20c3f4…128c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x5c35f6e3…1de4

0x065c9d…c394

4 touches
1 conflict

0x00000000…0004

0xd0f8a6…badc

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x7cb2f3fa…4836

0x34b655…2a6f

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

1 conflict on slot 0x80a503f8ae…46b088

← previous block·next block →recent activity