← previous blocknext block →recent activity

Analyzing

Block #71,090,577

15 transactions · 13 stateful · 2026-04-28 13:36:01 UTC

Parallelism

73/100

Blocked

31%

Avg conflicts / tx

0.47

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #71,090,577  ·  15 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0xb378025c…30cf

0x34b655…2a6f

4 touches
1 conflict

0x52c63247…ce02

0x0a3323…0a3c

4 touches
1 conflict

0x446f2734…8b54

0x0a3323…0a3c

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x3eadb0b6…d2f7

0x34b655…2a6f

4 touches
1 conflict

0xa141cb81…4890

0x73ada1…8be0

2 touches
0 conflicts

0xa9274bfd…c13d

0x73ada1…8be0

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity