← previous blocknext block →recent activity

Analyzing

Block #71,092,157

27 transactions · 24 stateful · 2026-04-28 13:46:33 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.59

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #71,092,157  ·  27 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x17606ba6…1b6e

0x754704…b603

8 touches
6 conflicts

0x8c49c85c…ee96

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0002

0xb857c1…9be1

6 touches
3 conflicts

0xa0f29ef3…1ffe

0xd32edf…ff58

5 touches
3 conflicts

0x085df2c1…305a

0x34b655…2a6f

4 touches
1 conflict

0x11f25e19…8bb1

0x34b655…2a6f

4 touches
1 conflict

0x1952c598…df64

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

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: 0x754704bc…afb603

6 conflicts on slot 0x17606ba612…ea1b6e

← previous block·next block →recent activity