Block #71,094,898

← previous blocknext block →recent activity

Analyzing

Block #71,094,898

10 transactions · 9 stateful · 2026-04-28 14:04:49 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,094,898  ·  10 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

0xbfca3cd0…5023

0x34b655…2a6f

4 touches
1 conflict

0x664bf99e…0a8c

0x34b655…2a6f

4 touches
1 conflict

0x016bd8f2…c85a

0x34b655…2a6f

2 touches
0 conflicts

0x01931e76…d502

0x34b655…2a6f

2 touches
0 conflicts

0x07934424…5b9c

0x34b655…2a6f

2 touches
0 conflicts

0x0c1bb03f…b4d1

0x34b655…2a6f

2 touches
0 conflicts

0x15c9b5bf…f732

0x34b655…2a6f

2 touches
0 conflicts

0x1ae7def3…515c

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: 0x34b6552d…112a6f

1 conflict on slot 0xbfca3cd067…cd5023

← previous block·next block →recent activity