← previous blocknext block →recent activity

Analyzing

Block #71,648,434

17 transactions · 16 stateful · 2026-05-01 03:35:01 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,648,434  ·  17 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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x1952c598…df64

0x34b655…2a6f

4 touches
1 conflict

0x1d731f70…4557

0x34b655…2a6f

4 touches
1 conflict

0x37379933…2402

0x34b655…2a6f

4 touches
1 conflict

0x4546ebad…b908

0x34b655…2a6f

4 touches
1 conflict

0x8d0e98f3…7ba0

0x34b655…2a6f

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity