← previous blocknext block →recent activity

Analyzing

Block #71,449,111

11 transactions · 10 stateful · 2026-04-30 05:24:04 UTC

Parallelism

82/100

Blocked

10%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #71,449,111  ·  11 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

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x451e482b…7e7d

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x11e1e2a4…54fb

0x34b655…2a6f

2 touches
0 conflicts

0x23114fac…630a

0x34b655…2a6f

2 touches
0 conflicts

0x3254d19b…f714

0x34b655…2a6f

2 touches
0 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

2 touches
0 conflicts

0x414e9446…4b59

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 0x085df2c147…d2305a

← previous block·next block →recent activity