← previous blocknext block →recent activity

Analyzing

Block #71,176,547

12 transactions · 11 stateful · 2026-04-28 23:08:38 UTC

Parallelism

75/100

Blocked

27%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #71,176,547  ·  12 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

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0xbae1dc61…fc1b

0x065c9d…c394

3 touches
1 conflict

0x2914398e…fed3

0xd32edf…ff58

3 touches
1 conflict

0x0772fc46…a916

0x34b655…2a6f

2 touches
0 conflicts

0x2484cc15…5afc

0x34b655…2a6f

2 touches
0 conflicts

0x3384af2a…cab7

0x34b655…2a6f

2 touches
0 conflicts

0x50c2960c…5f37

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: 0x8d66a43f…113095

1 conflict on slot 0x8a35acfbc1…6bd1ae

← previous block·next block →recent activity